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  linux.site:/home/reggie/work/mysql-5.1

We changed the error message to more clearly reflect the fact
that we are counting parts and subparts

into  mysql.com:/home/kostja/mysql/mysql-5.1-merge

into  mysql.com:/usr/local/home/marty/MySQL/mysql-5.1-new

into  mysql.com:/home/ndbdev/jmiller/clones/mysql-5.1-new

into  mysql.com:/usr/local/home/marty/MySQL/mysql-5.1-new

into  mysql.com:/home/kostja/mysql/mysql-5.1-merge

The problem was that error flag was not reset.

into  mysql.com:/home/cps/mysql/trees/5.1/5.1-virgin-no-debug

into  mysql.com:/usr/local/home/marty/MySQL/mysql-5.1-new

  Fix insert performance with mmap

into mysql.com:/home/hf/work/mysql-5.1.clean

into mysql.com:/home/hf/work/mysql-5.1.clean

into  mysql.com:/opt/local/work/mysql-5.0-runtime

into  mysql.com:/home/ndbdev/jmiller/clones/mysql-5.1-new

    This is a re-clone after tagging, so the version must be set back to 5.1.7-beta.

into  linux.site:/home/reggie/work/mysql-5.1-bug15408

into  mysql.com:/home/cps/mysql/devel/im/5.0-im-fix-race

duration of the whole 'flush instances'. As a consequence,
it was possible to query instance map, while it is in the
inconsistent state. The patch was reworked after review.

into  mysql.com:/usr/local/home/marty/MySQL/mysql-5.1-new

into  mysql.com:/home/cps/mysql/devel/im/5.0-im-add-error-message

connections correctly".
Recommit with the max timeout value in sync with the comment.

into  april.(none):/home/svoj/devel/mysql/BUG17116/mysql-5.1-new

pushing. the code needs to be more stable.

into  mysql.com:/space/pekka/ndb/version/my51

into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new

into  mysql.com:/space/pekka/ndb/version/my51

post-review fixes