into  zippy.cornsilk.net:/home/cmiller/work/mysql/bug19356/my51-bug19356

into  zippy.cornsilk.net:/home/cmiller/work/mysql/bug19356/my51-bug19356

The executing code had a safety assertion so that it refused to free Items
that it didn't create.  However, there is a case, undefined user variables,
which would put Items into the list to be freed.

Instead, do something that is more risky in expectation that the code will 
be refactored soon, as Kostja wants to do:  Remove the assertions from 
prepare() and execute().  Put one assertion at a higher level, before 
stmt->set_params_from_vars(), which may then create new to-be-freed Items .

into  rolltop.ignatz42.dyndns.org:/mnt/storeage/mysql-5.1-maint

into  rolltop.ignatz42.dyndns.org:/mnt/storeage/bug19024/my51-bug19024

  
The server variable warning_count should include the number of warnings, errors and notes according to the manual

into  neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint

  After merge fix.
field.cc:
  After merge fix

into  neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint

into  moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-real-bug21726

into  neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint

into  neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint

into  mysql.com:/usr/home/bar/mysql-5.0-rpl

into  mysql.com:/usr/home/bar/mysql-4.1-rpl

into  mysql.com:/usr/home/ram/work/bug22271/my51-bug22271

into  mysql.com:/usr/home/ram/work/bug22271/my51-bug22271

into  neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint

into  siva.hindu.god:/usr/home/tim/m/bk/wl3516/51

into  mockturtle.local:/home/dlenev/src/mysql-5.1-rt-merge

into  moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-real-bug21726

into  mockturtle.local:/home/dlenev/src/mysql-5.1-rt-merge

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

into  moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-bug21081

into  mysql.com:/users/lthalmann/bkroot/mysql-5.1-new-rpl

into  mysql.com:/users/lthalmann/bk/MERGE/mysql-5.1-merge

into  mysql.com:/users/lthalmann/bk/MERGE/mysql-5.0-merge

into  romeo.(none):/home/bk/fix-mysql-5.1-new-rpl

When compiling with qcc on QNC the define __GNUC__will be set although it doesn't support full GNU syntax
 - disable __attribute__ when using qcc

Adding test case.

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

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

into  moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-real-bug21726

Non-upper-level INSERTs (the ones in the body of stored procedure,
stored function, or trigger) into a table that have AUTO_INCREMENT
column didn't affected the result of LAST_INSERT_ID() on this level.

The problem was introduced with the fix of bug 6880, which in turn was
introduced with the fix of bug 3117, where current insert_id value was
remembered on the first call to LAST_INSERT_ID() (bug 3117) and was
returned from that function until it was reset before the next
_upper-level_ statement (bug 6880).

The fix for bug#21726 brings back the behaviour of version 4.0, and
implements the following: remember insert_id value at the beginning
of the statement or expression (which at that point equals to
the first insert_id value generated by the previous statement), and
return that remembered value from LAST_INSERT_ID() or @@LAST_INSERT_ID.

Thus, the value returned by LAST_INSERT_ID() is not affected by values
generated by current statement, nor by LAST_INSERT_ID(expr) calls in
this statement.

Version 5.1 does not have this bug (it was fixed by WL 3146).