After trying multiple inheritance (to messy and hard make it work) and
  sublassing jump_if_not (worked, but ugly), decided to on this solution
  instead:
  Inserting an abstract sp_instr_opt_meta class as parent for all instructions
  with destinations makes it possible to handle a continuation pointer for
  sp_instr_set_case_expr too.
  Note: No special test case; the fix is captured by the changed behaviour of
  bug14643_2, and bug14498_4 (formerly disabled), in sp.test.

into  mysql.com:/users/lthalmann/bk/mysql-5.0-bug16487

into  zim.tangent.org:/home/brian/mysql/mysql-5.0

into mysql.com:/M50/bug16730-5.0

Complaint from a user who was getting sick of repairing their tables do to their lousy setup (their words). All crashed archive tables will now be repaired on open. 

  - BUG#15166: Wrong update permissions required to execute triggers
  - BUG#15196: Wrong select permission required to execute triggers

The idea of the fix is to check necessary privileges
in Item_trigger_field::fix_fields(), instead of having "special variables"
technique. To achieve this, we should pass to an Item_trigger_field instance
a flag, which will indicate the usage/access type of this trigger variable.

into  mysql.com:/usr_rh9/home/elkin.rh9/MySQL/mysql-5.0

  Fill schema tables with data before filesort if it's necessary

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

  to skip directories which are not allowed for read

into  mysql.com:/usr_rh9/home/elkin.rh9/MySQL/mysql-5.0

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

into  mysql.com:/usr_rh9/home/elkin.rh9/MySQL/mysql-5.0

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

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

  
Since replication rules execute after `mysql_multi_update_prepare' returns we
delay to `break' in case this functions returns non-zero (some tables are not found) 
for to examine if there is an ignore rule for a not-found table. By doing that
it is guaranteed do/ignore replication rules logically preceed opening table routine.

Fixed that UPDATE statement crashes multi-byte charset fulltext index.

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

into  zim.tangent.org:/home/brian/mysql/mysql-5.0

into eagle.intranet.mysql.r18.ru:/home/hf/work/mysql-4.1.mrg

into eagle.intranet.mysql.r18.ru:/home/hf/work/mysql-4.1.mrg

into eagle.intranet.mysql.r18.ru:/home/hf/work/mysql-4.1.mrg

Turns out that the bulk interface was not well documented. I fixed the issue in archive and I will go and update the comments in handler next. I should probably also look through the other engines and see if this an issue elsewhere as well. 

in the Binary Log.

The bug appears after implementation of WL#2984
(Make stored routine variables work according to the standard).

  Lowered the parameter to 10, and also renamed non-standard table names to t3.

into  mysql.com:/extern/mysql/work/bug15658/mysql-5.0

into  mysql.com:/extern/mysql/work/bug15658/mysql-5.0

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

into  mysql.com:/extern/mysql/work/bug15658/mysql-5.0