In the rare circumstance where a mysqld connects to a mgm server, then the
mgm server goes away before a node id can be allocated, it was possible to get
an Error in mgm protocol parser error message.

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

  BUG#12701: SHOW VARIABLES does not show correct size of buffer pool.
ha_innodb.cc:
  BUG#12701: SHOW VARIABLES does not show correct size of buffer pool

incorrect warning on open cursor"

into  mysql.com:/home/dlenev/src/mysql-5.0-bg13399-2

which is now dropped" and bug #12329 "Bogus error msg when executing PS with
stored procedure after SP was re-created".

function with a cursor". Enable execution of SELECT queries in SP on slave.

into  mysql.com:/export/space/pekka/ndb/version/my50

into production.mysql.com:/usersnfs/istruewing/autopush/mysql-5.0

into production.mysql.com:/usersnfs/istruewing/autopush/mysql-5.0

After merge fix.

into  mysql.com:/export/space/pekka/ndb/version/my50

Issuing error about presence of commit/rollback statements in stored functions and triggers added to SP parsing procedure (BUG#13627)

The crash mentioned in original bug report is already prevented by one
of previous patches (fix for bug #13343 "CREATE|etc TRIGGER|VIEW|USER
don't commit the transaction (inconsistency)"), this patch only improve
error returning.

  Auto merged

into  mysql.com:/home/mydev/mysql-5.0-5000

into  mysql.com:/home/mydev/mysql-5.0-5000

Version for 5.0.
It fixes three problems:
1. The cause of the bug was that we did not check the table version for
 the HANDLER ... READ commands. We did not notice when a table was
 replaced by a new one. This can happen during ALTER TABLE, REPAIR
 TABLE, and OPTIMIZE TABLE (there might be more cases). I call the fix
 for this problem "the primary bug fix".
2. mysql_ha_flush() was not always called with a locked LOCK_open.
 Though the function comment clearly said it must.
 I changed the code so that the locking is done when required. I call
 the fix for this problem "the secondary fix".
3. In 5.0 (not in 4.1 or 4.0) DROP TABLE had a possible deadlock flaw in
 concur with FLUSH TABLES WITH READ LOCK. I call the fix for this
 problem "the 5.0 addendum fix".

into  sanja.is.com.ua:/home/bell/mysql/bk/work-bug6-5.0

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

into  sanja.is.com.ua:/home/bell/mysql/bk/work-bug6-5.0

into  mysql.com:/home/mydev/mysql-4.1-4100

After merge fix.

into  mysql.com:/home/mydev/mysql-4.0-4000

into  mysql.com:/home/mydev/mysql-4.1-4100

into  mysql.com:/usr/home/pem/bug14723/mysql-5.0

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

test_if_order_by_key() expected only Item_fields to be in order->item, thus
failing to find available index on view's field, which results in reported
error.

Now test_if_order_by_key() calls order->item->real_item() to get field for
choosing index.

Item_ref's null_value wasn't updated in save_org_in_field() causing reported
error.

into  selena.:H:/MYSQL/src/#14569-mysql-5.0

into  mysql.com:/usr/home/pem/bug14723/mysql-5.0

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

into  selena.:H:/MYSQL/bkt/mysql-5.0