The problem happened because "mysql" didn't send mysql_select_db() if 
the current active database was specified in USE.
Now it always send mysql_select_db().
Rebuilding of completion hash is skipped in the same db is used
(for performance purposes).

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  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.

into mysql.com:/Users/kent/mysql/bk/mysql-5.0-new

  Always compile position independent

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

into  devsrv-b.mysql.com:/users/msvensson/mysql-5.0

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

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

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

 - A segfault occured when the function 'kill_server' called 
   'my_sigset' with signal number 0. 'my_sigset' is a macro which
   uses 'sigaction' to install the signal handler with an invalid
   signal number will on most platforms return EINVAL but yields
   a segfauilt on IRIX 6.5
 - The server crash was detected by mysqld_safe and it was restarted although
   a shutdown was requested. 
 - Semantics of kill_server(0) is not known, leaving it intact

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.0