restore CREATE TABLE ... TYPE=engine until 5.2

into  mysql.com:/home/bk/fix-mysql-5.1-release

xml.result:
  Adding test for Bug #16312 XML: extractvalue() crash if angle brackets,
  A fix for #16234 fixed this bug automatically.

into  mysql.com:/home/my/mysql-5.1

Don't run upgrade.test with embedded server as it requires mysqlcheck

into  mysql.com:/home/my/mysql-5.1

into  zim.(none):/home/brian/mysql/dep-5.1

This patch handles compiles with threads, namely if you don't have pthreads it will remove support for threads in the applications (and it is fixed in such a way that tests won't break).

into  mysql.com:/home/mysql_src/mysql-5.1-new

and new binlog format called "mixed" (which is statement-based except if only row-based is correct,
in this cset it means if UDF or UUID is used; more cases could be added in later 5.1 release):
SET GLOBAL|SESSION BINLOG_FORMAT=row|statement|mixed|default;
the global default is statement unless cluster is enabled (then it's row) as in 5.1-alpha.
It's not possible to use SET on this variable if a session is currently in row-based mode and has open temporary tables (because CREATE
TEMPORARY TABLE was not binlogged so temp table is not known on slave),  or if NDB is enabled (because
NDB does not support such change on-the-fly, though it will later), of if in a stored function (see below).
The added tests test the possibility or impossibility to SET, their effects, and the mixed mode,
including in prepared statements and in stored procedures and functions.
Caveats:
a) The mixed mode will not work for stored functions: in mixed mode, a stored function will
always be binlogged as one call and in a statement-based way (e.g. INSERT VALUES(myfunc()) or SELECT myfunc()).
b) for the same reason, changing the thread's binlog format inside a stored function is
refused with an error message.
c) the same problems apply to triggers; implementing b) for triggers will be done later (will ask
Dmitri).
Additionally, as the binlog format is now changeable by each user for his session, I remove the implication
which was done at startup, where row-based automatically set log-bin-trust-routine-creators to 1
(not possible anymore as a user can now switch to stmt-based and do nasty things again), and automatically
set --innodb-locks-unsafe-for-binlog to 1 (was anyway theoretically incorrect as it disabled
phantom protection).
Plus fixes for compiler warnings.

into  mysql.com:/home/my/mysql-5.1

- Added empty constructors and virtual destructors to many classes and structs
- Removed some usage of the offsetof() macro to instead use C++ class pointers

into  zim.(none):/home/brian/mysql/dep-5.1

Someone modified the output to explain but did not run all tests before pushing, otherwise they would have realized that they broke this test.

AKA someone pushed without testing.

into  zim.(none):/home/brian/mysql/dep-5.1

This patch cleans up two tests which were a bit fragile from other failing tests. It also removes some variables associated with removed RAID support.

(Needed for "list of pushes" web page and autopush)

into lmy004.:/work/mysql-5.1-bug16411

fix for bug#16411

last fixes

into moonbone.local:/work/17530-bug-5.0-mysql

into  mysql.com:/usr/local/mysql/mysql-5.1-new

(Backported from mysql-5.1-new)

fix for bug #16412 (post-merge fix)

into moonbone.local:/work/17530-bug-5.0-mysql

into lmy004.:/work/mysql-5.1-bug16412