post-review fixes

WL#1032
sql_mode setting was disregarded during create/alter event and wasn't set during
event execution.
(post-review small fixes)

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

into mysql.com:/home/psergey/mysql-5.1-look

if we've got a tree of type ALWAYS or MAYBE.

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

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

Fixes failing sp.test

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

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

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

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

- test tables use blobs without PK, and was not handled correctly

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

fails with --vardir option.

  Fix online ordered index build of varsize table

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new

into  rurik.mysql.com:/home/igor/dev/mysql-5.1-0

into mysql.com:/Users/kent/mysql/bk/mysql-5.1-new

  Reintroduced a max build
  Limited testing of 'debug' and 'max' servers
  Berkeley DB only in 'max'

into mysql.com:/Users/kent/mysql/bk/mysql-5.1-new

  Added --restart-cleanup option
drop-on-restart.inc:
  DROP commands to cleanup on restart
  new file
mysqltest.c:
  Added option --include=<sql-file>

We had a number of tests where there were no bugs related to disabling of tests, bugs were fixed, or no clear discription or plan.

into  zim.tangent.org:/home/brian/mysql/dep-5.1

Fixed some threading issues that Guilhem found (and its what I get for copy and pasting from elsewhere without thinking about it). Added depracted messages to BACKUP, RESTORE, and LOAD TABLE FROM MASTER (which doesn't work well). 

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

"mysqldump" test fails (mysqlimport related, Brian aware), ndb_cache2 ndb_cache_multi2
partition_mgm_err fail (unrelated to my changes), rpl_row_view01 (known crash BUG#17265)

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

into  mysql.com:/home/mysql_src/mysql-5.1-new; will fix manually sp_head.cc and mysqld.cc later soon.

Fix for BUG#13897 "failure to do SET SQL_MODE=N where N is a number > 31" (the original bug's title isn't the simplest
symptom). sys_var::check_set() was wrong. mysqlbinlog makes use of such SET SQL_MODE=N
(where N is interpreted like if SQL_MODE was a field of type SET), so
this bug affected recovery from binlogs if the server was running with certain SQL_MODE values,
for example the default values on Windows (STRICT_TRANS_TABLES); to work around this bug people
had to edit mysqlbinlog's output.