into moonbone.local:/work/mysql-5.0-bug-11760

by subtime() in view

Item_func_add_time::print() were printing arg[0] instead of arg[1] which
results in wrongly created view. Functions addtime() and subtime were
affected by this bug.

into  mysql.com:/data0/emurphy/src/mysql-5.0

  BUG#12040 Fixed compile failure by using %p instead of %x to print a pointer in DBUG_PRINT

  Delete: mysql-test/var

into  mysql.com:/home/kostja/mysql/mysql-5.0-10760-new

The idea of the patch
is that every cursor gets its own lock id for table level locking.
Thus cursors are protected from updates performed within the same 
connection. Additionally a list of transient (must be closed at
commit) cursors is maintained and all transient cursors are closed
when necessary. Lastly, this patch adds support for deadlock
timeouts to TLL locking when using cursors.
+ post-review fixes.

into  mysql.com:/home/dlenev/src/mysql-5.0-tn

into  mysql.com:/home/dlenev/src/mysql-5.0-tn

into  mysql.com:/home/jimw/my/mysql-5.0-clean

  "Triggers have the wrong namespace"
  "Triggers: duplicate names allowed"
  "Triggers: CREATE TRIGGER does not accept fully qualified names"
  "SHOW TRIGGERS"

This patch allows to configure MyISAM for 128 indexes per table.
The main problem is the key_map, wich is implemented as an ulonglong.
To get rid of the limit and keep the efficient and flexible
implementation, the highest bit is now used for all upper keys.
This means that the lower keys can be disabled and enabled 
individually as usual and the high keys can only be disabled and
enabled as a block. That way the existing test suite is still
applicable, while more keys work, though slightly less efficient.
To really get more than 64 keys, some defines need to be changed.
Another patch will address this.

  fixed BLOB, TEXT(wrong maximum length), BIT and integer types(wrong numeric_precision value)

into mysql.com:/home/gluh/MySQL/Merge/5.0

   changed 'SHOW PROCEDURE' behavoiur to be like INFORMATION_SCHEMA.routines

list.

into  mysql.com:/Users/emurphy/src/work/mysql-5.0-bug11567

into  radha.local:/Users/patg/mysql-build/mysql-5.0

into  mysql.com:/home/jimw/my/mysql-5.0-readline

as well as changes to the test.

into  mysql.com:/Users/emurphy/src/work/mysql-5.0-bug11567

into  mysql.com:/home/kostja/mysql/mysql-5.0-merge

get_defaults_file() -> get_defaults_options()

into  mishka.local:/home/my/mysql-5.0

into moonbone.local:/work/mysql-5.0-bug-11482

into moonbone.local:/work/mysql-5.0-bug-11482

into lmy002.wdf.sap.corp:/home/georg/work/mysql/prod/mysql-5.0

  Changed test case comment to be more meaningful

  than in previous 4.1.x

Wrongly applied optimization were adding NOT NULL constraint which results in
rejecting valid rows and reduced result set.

The problem was that add_notnull_conds() while checking subquery were adding
NOT NULL constraint to left joined table, to which, normally, optimization 
don't have to be applied.