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  sin.intern.azundris.com:/home/tnurnberg/31253/51-31253

after-merge fixies

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

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

into  pilot.mysql.com:/data/msvensson/mysql/mysql-5.0-maint

into  pilot.mysql.com:/data/msvensson/mysql/mysql-5.0-maint

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

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

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

Write .reject file to r/ if it's writable else use opt_logdir 

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

 - "mysqld --verbose --help" need to be started in a writable directory 

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

 - Allow test case names to be specied in various different ways

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

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

convert(<invalid time>, datetime) in WHERE caused crash as function
returned (void*)NULL, but did not flag SQL NULL. It does now.

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

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

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

Reserve the space for the leading 0 (before the decimal point) in DECIMAL(a,a) ZEROFILL.

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

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

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

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  mysql.com:/home/ram/work/b31070/b31070.5.0

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

Issue a warning if a user sets an option or a variable to a value that is greater than a defined maximum for the option/variable.

This is for bug #29446 "Specifying a myisam_sort_buffer > 4GB on 64 bit machines not possible". Support for myisam_sort_buffer_size > 4 GB on 64-bit Windows will be looked at later in 5.2.

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

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