into  olga.mysql.com:/home/igor/mysql-5.1-opt

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

  Corrected test case for the bug#27878.

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

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

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

database.

If a user has a right to update anything in the current database then the 
access was granted and further checks of access rights for underlying tables
wasn't done correctly. The check is done before a view is opened and thus no
check of access rights for underlying tables can be carried out.
This allows a user to update through a view a table from another database for
which he hasn't enough rights.

Now the mysql_update() and the mysql_test_update() functions are forces
re-checking of access rights after a view is opened.

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

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

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

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

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

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

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

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

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

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

Bug occurs in INSERT IGNORE ... SELECT ... ON DUPLICATE KEY UPDATE
statements, when SELECT returns duplicated values and UPDATE clause
tries to assign NULL values to NOT NULL fields.
NOTE: By current design MySQL server treats INSERT IGNORE ... ON
DUPLICATE statements as INSERT ... ON DUPLICATE with update of
duplicated records, but MySQL manual lacks this information.
After this fix such behaviour becomes legalized.

The write_record() function was returning error values even within
INSERT IGNORE, because ignore_errors parameter of
the fill_record_n_invoke_before_triggers() function call was
always set to FALSE. FALSE is replaced by info->ignore.

ref access to a less expensive range access. 
This occurred only with InnoDB tables.

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

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

test result fixed

Item_decimal_typecast::print properly implemented

into  bk-internal.mysql.com:/data0/bk/mysql-5.1-opt

Missing check for overflow added to the Item_decimal_typecast::val_decimal

into  bk-internal.mysql.com:/data0/bk/mysql-5.1-opt

  A test case is corrected.

into  olga.mysql.com:/home/igor/mysql-5.1-opt

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

TIMESTAMP field when no value has been provided.

The LOAD DATA sets the current time in the TIMESTAMP field with
CURRENT_TIMESTAMP default value when the field is detected as a null.
But when the LOAD DATA command loads data from a file that doesn't contain
enough data for all fields then the rest of fields are simply set to null
without any check. This leads to no value being inserted to such TIMESTAMP
field.

Now the read_sep_field() and the read_fixed_length() functions set current
time to the TIMESTAMP field with CURRENT_TIMESTAMP default value in all cases
when a NULL value is loaded to the field.

  After merge fix.

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