Merge with 5.0-opt.

into  gleb.loc:/home/uchum/work/bk/mysql-5.1-opt

into  olga.mysql.com:/home/igor/dev-opt/mysql-5.0-opt-bug28571

constant outer tables did not return null complemented
rows when conditions were evaluated to FALSE.
Wrong results were returned because the conditions over constant
outer tables, when being pushed down, were erroneously enclosed 
into the guard function used for WHERE conditions.

  Warnings elimination.

into  gleb.loc:/home/uchum/work/bk/mysql-5.0-opt

sometimes `mysqldump --hex-blob' overruned output buffer by '\0' byte.

The dump_table() function has been fixed to reserve 1 byte more for the
last '\0' byte of dumped string.

into  olga.mysql.com:/home/igor/dev-opt/mysql-5.0-opt-bug28561

CHECK OPTION and a subquery in WHERE condition.
The abort was triggered by setting the value of join->tables for
subqueries in the function JOIN::cleanup. This function was called
after an invocation of the JOIN::join_free method for subqueries
used in WHERE condition.

into  moonbone.local:/mnt/gentoo64/work/27563-bug-5.0-opt-mysql

If a stored function or a trigger was killed it had aborted but no error
was thrown. This allows the caller statement to continue without a notice.
This may lead to a wrong data being inserted/updated to/deleted as in such
cases the correct result of a stored function isn't guaranteed. In the case
of triggers it allows the caller statement to ignore kill signal and to
waste time because of re-evaluation of triggers that always will fail
because thd->killed flag is still on.

Now the Item_func_sp::execute() and the sp_head::execute_trigger() functions
check whether a function or a trigger were killed during execution and
throws an appropriate error if so.
Now the fill_record() function stops filling record if an error was reported
through thd->net.report_error.

  After merge fix.

into  moonbone.local:/mnt/gentoo64/work/test-5.1-opt-mysql

into  dl145s.mysql.com:/users/mhansson/mysql/autopush/mysql-5.0o-pushee

into  magare.gmz:/home/kgeorge/mysql/work/B28476-5.1-opt

Zero merge all except the new test

into  magare.gmz:/home/kgeorge/mysql/autopush/B28476-5.0-opt

When processing the USE/FORCE index hints
the optimizer was not checking if the indexes 
specified are enabled (see ALTER TABLE).
Fixed by:
 Backporting the fix for bug 20604 to 5.0

into  dl145s.mysql.com:/users/mhansson/mysql/push/bug23856/mysql-5.0o-pushee

into  dl145s.mysql.com:/users/mhansson/mysql/push/bug23856/mysql-5.1o-pushee

mode.

When a new DATE/DATETIME field without default value is being added by the
ALTER TABLE the '0000-00-00' value is used as the default one. But it wasn't
checked whether such value was allowed by the set sql mode. Due to this
'0000-00-00' values was allowed for DATE/DATETIME fields even in the
NO_ZERO_DATE mode.

Now the mysql_alter_table() function checks whether the '0000-00-00' value
is allowed for DATE/DATETIME fields by the set sql mode.
The new error_if_not_empty flag is used in the mysql_alter_table() function
to indicate that it should abort if the table being altered isn't empty.
The new new_datetime_field field is used in the mysql_alter_table() function
for error throwing purposes. 
The new error_if_not_empty parameter is added to the copy_data_between_tables()
function to indicate the it should return error if the source table isn't empty.

into  mysql.com:/home/hf/work/27984/my51-27984

into  mysql.com:/home/hf/work/27984/my51-27984

into  mysql.com:/home/hf/work/27984/my50-27984

into  mysql.com:/home/hf/work/27984/my50-27984

into  mysql.com:/home/hf/work/27984/my51-27984

into  mysql.com:/home/hf/work/27984/my51-27984

decimal_round failed to perform a correct rounding 
of a decimal number if its first nine digits were '9'.
It just sets those digits to 0.

into  mysql.com:/home/hf/work/28361/my50-28361

into  mysql.com:/home/hf/work/28361/my51-28361

into  dl145s.mysql.com:/users/mhansson/mysql/push/bug23856/my51-bug23856

into  mysql.com:/home/hf/work/27894/my50-27894

into  mysql.com:/home/hf/work/27894/my51-27894

into  mysql.com:/home/hf/work/27894/my51-27894

result max length changed for the 'decimal' fields
so test results have to be fixed

into  magare.gmz:/home/kgeorge/mysql/work/B22855-5.1-opt

into  magare.gmz:/home/kgeorge/mysql/work/B22855-5.0-opt