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

into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.0-ndb-merge

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

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

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

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

into  dl145h.mysql.com:/data0/mkindahl/mysql-5.1

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

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

into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.0-ndb-merge

default changed not to run idempotent, but test requires it because of how ndb logs updates as write

(originally from Mats)

(originally from Mats)

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

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

because it uses BINLOG statement, which is not supported in embedded mode.
Fix: disable the test in embedded mode.

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

Problem: mysqlbinlog does not free memory if an error happens.
Fix: binlog-processing functions do not call exit() anymore. Instead, they
print an error and return an error code. Error codes are propagated all
the way back to main, and all allocated memory is freed on the way.

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

  fix failing autotest-test

simply killed.

  Using more than 16g can cause record-pool ptr.i values to overflow
  Fix by splitting memory into 2 zones, lo(16g)/hi(rest)
  When record pools only use zone_lo, and datamemory, buffers etc...can use any

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.