into  mysql.com:/home/bar/mysql-5.0.b24478

into  mysql_cab_desk.:C:/source/c++/mysql-5.0-rpl

Problem: DROP TRIGGER was not properly handled in combination
with slave filters, which made replication stop
Fix: loading table name before checking slave filters when
dropping a trigger.

into  mysql.com:/nfsdisk1/lars/MERGE/mysql-5.0-merge

into  mysql.com:/nfsdisk1/lars/MERGE/mysql-5.0-merge

into  mysql.com:/nfsdisk1/lars/MERGE/mysql-4.1-merge

into  mysql.com:/nfsdisk1/lars/MERGE/mysql-5.0-merge

into  mysql.com:/nfsdisk1/lars/MERGE/mysql-5.0-merge

into  mysql.com:/nfsdisk1/lars/MERGE/mysql-4.1-merge

into  mysql_cab_desk.:C:/source/c++/mysql-5.0_BUG_20141

           Triggers in SBR mode."
BUG#14914 "SP: Uses of session variables in routines are not always
           replicated"
BUG#25167 "Dupl. usage of user-variables in trigger/function is not
           replicated correctly"

User-defined variables used inside of stored functions/triggers in
statements which did not update tables directly were not replicated.
We also had problems with replication of user-defined variables which
were used in triggers (or stored functions called from table-updating
statements) more than once.

This patch addresses the first issue by enabling logging of all
references to user-defined variables in triggers/stored functions
and not only references from table-updating statements.

The second issue stemmed from the fact that for user-defined
variables used from triggers or stored functions called from
table-updating statements we were writing binlog events for each
reference instead of only one event for the first reference.
This problem is already solved for stored functions called from
non-updating statements with help of "event unioning" mechanism.
So the patch simply extends this mechanism to the case affected.
It also fixes small problem in this mechanism which caused wrong
logging of references to user-variables in cases when non-updating
statement called several stored functions which used the same
variable and some of these function calls were omitted from binlog
as they were not updating any tables.

  "INSERT... ON DUPLICATE KEY UPDATE skips auto_increment values"
didn't make it into 5.0.36 and 5.1.16,
so we need to adjust the bug-detection-based-on-version-number code.
Because the rpl tree has a too old version, rpl_insert_id cannot pass,
so I disable it (like is already the case in 5.1-rpl for the same reason),
and the repl team will re-enable it when they merge 5.0 and 5.1 into
their trees (thus getting the right version number).

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

Suppress compiler warnings from bdb and (for the moment) warnings from ndb

Fixed a couple of usage of not initialized warnings (unlikely cases)

This also fixes a bug in counting number of rows that are updated when we have many simultanous queries

into  trift2.:/MySQL/M50/push-5.0

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

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

Fixed that --extern works with mysql-test-run.pl
Small trivial cleanups

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

into  trift2.:/MySQL/M50/merge-5.0

into  bk-internal.mysql.com:/data0/bk/mysql-5.0-engines

The declaration of "thr_client_alarm" had got lost, keep it in "mysys/thr_alarm.c".

into  trift2.:/MySQL/M41/merge-4.1

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

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

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

  forgott to add testcase for bug#26481

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

  fix for killed node during initial node restart

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

  master failure during master take over

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

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