into  polly.(none):/home/kaa/src/maint/mysql-5.1-maint

into  polly.(none):/home/kaa/src/maint/mysql-5.1-maint

into  polly.(none):/home/kaa/src/maint/mysql-5.0-maint

into  polly.(none):/home/kaa/src/maint/mysql-5.0-maint

into  polly.(none):/home/kaa/src/maint/mysql-4.1-maint

into  polly.(none):/home/kaa/src/maint/bug28878/my51-bug28878

into  polly.(none):/home/kaa/src/maint/bug28878/my50-bug28878

into  ramayana.hindu.god:/home/tsmith/m/bk/maint/51

into  mysql.com:/home/ram/work/b29444/b29444.5.1

into  ramayana.hindu.god:/home/tsmith/m/bk/maint/51

into  ramayana.hindu.god:/home/tsmith/m/bk/maint/50

into  ramayana.hindu.god:/home/tsmith/m/bk/maint/51

into  ramayana.hindu.god:/home/tsmith/m/bk/maint/51

into  ramayana.hindu.god:/home/tsmith/m/bk/maint/50

into  mysql.com:/home/ram/work/mysql-5.1-maint

into  mysql.com:/home/ram/work/mysql-5.1-maint

as PS protocol gives slightly different metadata.

into  ramayana.hindu.god:/home/tsmith/m/bk/maint/51

into  zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0-maint

Problem: creating a partitioned table during name resolution for the 
partition function we search for column names in all parts of the
CREATE TABLE query. It is superfluous (and wrong) sometimes.

Fix: launch name resolution for the partition function against
the table we're creating.

into  mysql.com:/home/ram/work/b31438/b31438.5.1

into  mysql.com:/home/ram/work/b31249/b31249.5.0

into  mysql.com:/home/ram/work/b31438/b31438.5.1

into  mysql.com:/home/ram/work/b31249/b31249.5.1

bitmap_is_set(table->write_set, fiel

Problem: creating a temporary table we allocate the group buffer if needed
followed by table bitmaps (see create_tmp_table()). Reserving less memory for 
the group buffer than actually needed (used) for values retrieval may lead 
to overlapping with followed bitmaps in the memory pool that in turn leads 
to unpredictable consequences.

As we use Item->max_length sometimes to calculate group buffer size,
it must be set to proper value. In this particular case 
Item_datetime_typecast::max_length is too small.

Another problem is that we use max_length to calculate the group buffer
key length for items represented as DATE/TIME fields which is superfluous.

Fix: set Item_datetime_typecast::max_length properly,
accurately calculate the group buffer key length for items 
represented as DATE/TIME fields in the buffer.

into  alf.(none):/src/bug28774/my50-bug28774

into  alf.(none):/src/bug28774/my51-bug28774

into  alf.(none):/src/bug28774/my51-bug28774

doesn't clean them up
- Make sure to cleanup temporary files after use.

into  alf.(none):/src/bug28535/my51-bug28535

- Fixed error message.

into  zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.1-maint

Problem: check missed if the second updatexml() argument is valid.

Fix: check it.

into  sin.intern.azundris.com:/home/tnurnberg/31253/51-31253

into  sin.intern.azundris.com:/home/tnurnberg/31253/50-31253

after-merge fixies

into  sin.intern.azundris.com:/home/tnurnberg/19828/50-19828

into  sin.intern.azundris.com:/home/tnurnberg/19828/51-19828

into  pilot.mysql.com:/data/msvensson/mysql/mysql-5.1-new-maint