into  quad.:/mnt/raid/alik/MySQL/devel/5.1-rt-merged

FK definition.

two timestamp fields.
  
The actual problem here was that CREATE TABLE allowed zero
date as a default value for a TIMESTAMP column in NO_ZERO_DATE mode.
  
The thing is that for TIMESTAMP date type specific rule is applied:
  column_name TIMESTAMP == column_name TIMESTAMP DEFAULT 0
whever for any other date data type
  column_name TYPE == column_name TYPE DEFAULT NULL
  
The fix is to raise an error when we're in NO_ZERO_DATE mode and
there is TIMESTAMP column w/o default value.

behave randomly with mysql_change_user.

The test case had to be moved into not_embedded_server.test file,
because SHOW GLOBAL STATUS does not work properly in embedded
server (see bug 34517).

but not collation.

The problem here was that text literals in a view were always
dumped with character set introducer. That lead to loosing
collation information.

The fix is to dump character set introducer only if it was
in the original query. That is now possible because there 
is no problem any more of loss of character set of string
literals in views -- after WL#4052 the view is dumped 
in the original character set.

behave randomly with mysql_change_user.
  
The problem was that global status variables were not updated
in THD::check_user(), so thread statistics were lost after
COM_CHANGE_USER.
  
The fix is to update global status variables with the thread ones
before preparing the thread for new user.

into  dl145h.mysql.com:/data0/mkindahl/mysql-5.0-rpl-merge

(originally from Mats)

(originally from Mats)

into  dl145h.mysql.com:/data0/mkindahl/mysql-5.0-rpl-merge

into  dipika.(none):/opt/local/work/mysql-5.1-runtime

Disable the test case.

into  dipika.(none):/opt/local/work/mysql-5.1-runtime

into  dipika.(none):/opt/local/work/mysql-5.1-runtime

into  dipika.(none):/opt/local/work/mysql-5.0-runtime

simply killed.

into  dipika.(none):/opt/local/work/mysql-5.1-runtime

into  mysql.com:/Users/davi/mysql/mysql-5.1-runtime

into  mysql.com:/Users/davi/mysql/mysql-5.1-runtime

The unsignedness of large integer user variables was not being
properly preserved when feeded to prepared statements. This was
happening because the unsigned flags wasn't being updated when
converting the user variable is converted to a parameter.

The solution is to copy the unsigned flag when converting the
user variable to a parameter and take the unsigned flag into
account when converting the integer to a string.

into  dipika.(none):/opt/local/work/mysql-5.1-runtime

table.

On crashes generate a user-friendly resolved and demangled stack
trace when libc provides the necessary functions (newer libc on i386,
x86_64, powerpc, ia64, alpha and s390). Otherwise print a numeric
stack trace as before, relying on resolve_stack_dump utility.

into  dipika.(none):/opt/local/work/mysql-5.1-runtime

into  mysql.com:/Users/davi/mysql/mysql-5.1-runtime

into  pilot.mysql.com:/data/msvensson/mysql/mysql-5.1-runtime

into  pilot.mysql.com:/data/msvensson/mysql/mysql-5.1-runtime

into  pilot.mysql.com:/data/msvensson/mysql/mysql-5.1-runtime

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