into  mysql.com:/space/pekka/ndb/version/my50-bug14509

into  april.(none):/home/svoj/devel/mysql/BUG17001/mysql-5.0

into  april.(none):/home/svoj/devel/mysql/BUG17001/mysql-5.0

into  mysql.com:/opt/local/work/mysql-5.0-runtime

  Stepped up to 5.0.23

into  april.(none):/home/svoj/devel/mysql/BUG17001/mysql-5.0

into  april.(none):/home/svoj/devel/mysql/BUG17001/mysql-5.0

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

Remove dflt_field from field structure as this was only needed when createing temporary table and I found another soultion that doesn't increase the size of the field structure for all table instances. (Better fix for bug #19089)
Fixed compiler warnings
Fixed valgrind warning in Item_date_add_intervall::eq. (Recoding of bugfix #19490)

into  april.(none):/home/svoj/devel/mysql/BUG18233/mysql-5.0

into  zippy.(none):/home/cmiller/work/mysql/mysql-5.0--bug11151

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0

not transaction-safe for stored procedures.  Related to Bug#11151.

into  april.(none):/home/svoj/devel/mysql/BUG18233/mysql-5.0

into  mysql.com:/usr/local/mysql/mysql-5.0

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0

transfer NO_DEFAULT_VALUE_FLAG flag to new field

 - Unlock the mutex after looking at rli->events_till_abort
 - Already fixed in 5.1 so it will be null merged.

show view definition to users that have the needed privilleges

into  rurik.mysql.com:/home/igor/dev/mysql-5.0-0

into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.0-main

into  mysql.com:/home/kgeorge/mysql/5.0/B18745

into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.0-main

into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.0-main

into  mysql.com:/home/stewart/Documents/MySQL/5.0/main

Moved the InnoDB related test from func_group.test to innodb_mysql.test

into mysql.com:/home/hf/work/mysql-5.0.mrg

into  rurik.mysql.com:/home/igor/dev/mysql-5.0-0

When a CREATE TABLE command created a table from a materialized
view id does not inherit default values from the underlying table.
Moreover the temporary table used for the view materialization
does not inherit those default values.
In the case when the underlying table contained ENUM fields it caused
misleading error messages. In other cases the created table contained
wrong default values.
The code was modified to ensure inheritance of default values for
materialized views.