While executing a trigger, we have to set thd->abort_on_warning to the value
it had at trigger creation time.

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

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

into  dl145j.mysql.com:/tmp/andrei/5.0-bug18715_drop_view_slave

into  mysql.com:/home/MySQL/5.0-Bug-17248a

into  mysql.com:/home/psergey/mysql-5.0-csc9139

get_best_covering_ror_intersect() was copying ror_scans starting from the 
end of the array and not from its beginning.

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

limit.

into  mysql.com:/home/tomash/src/mysql_ab/mysql-5.0-bug15933

CONNECTION_ID() was implemented as a constant Item, i.e. an instance of
Item_static_int_func class holding value computed at creation time.
Since Items are created on parsing, and trigger statements are parsed
on table open, the first connection to open a particular table would
effectively set its own CONNECTION_ID() inside trigger statements for
that table.

Re-implement CONNECTION_ID() as a class derived from Item_int_func, and
compute connection_id on every call to fix_fields().

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

into  mysql.com:/home/tomash/src/mysql_ab/mysql-5.0-bug15933

a race between updating and checking Max_used_connections.  This is done in
a loop until either disconnect finished or timeout expired.  In a latter case
the test will fail.

Fixed in parser. rpl_view gained no changes but rpl_view-slave.opt.

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

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

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

into  mysql.com:/usr/home/ram/work/5.0.b14360

into  mysql.com:/home/alexi/bugs/mysql-5.0-merge

 - Improved solution by adding an else stetment so that do find next is avoided if erorr occurs, but we still return zero files found instaed of an error

If the second or the third argument of a BETWEEN predicate was
a constant expression, like '2005.09.01' - INTERVAL 6 MONTH,
while the other two arguments were fields then the predicate 
was evaluated incorrectly and the query returned a wrong
result set.
The bug was introduced in 5.0.17 when in the fix for 12612.

into  mysql.com:/usr/home/ram/work/5.0.b14360

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

Add surrounding braces, move invalidate dictionary_cace to after declaration of variable "table_list"

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

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

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

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

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

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

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

into  mysql.com:/home/alexi/bugs/mysql-5.0-15868-work

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

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