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

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

bug#21873 MySQLD Crash on ALTER...ADD..UNIQUE..USING HASH statement for NDB backed table: Use passed key_info to check for nullable fields

  revert fix bug#21052 as it's wrong, and induces bus-error on node crashes

into  perch.ndb.mysql.com:/home/jonas/src/51-work

into  perch.ndb.mysql.com:/home/jonas/src/50-work

  Fix some too small buffers in backup
  

    Fix bug in restore with table with many columns, Compute size of databuffer pool correctly

    Add better error message if getting error in RESTORE

    when doing create unique index which mysql will silently converts to PK, ndb is not informed
    so table will be useless.
  
    change so that we never do online add index wo/ primary key.
    this is not good, but it's better than a useless table

into  perch.ndb.mysql.com:/home/jonas/src/51-work

into  perch.ndb.mysql.com:/home/jonas/src/50-work

  Fixed a 4.1/5.0 vs. 5.1 name change in latest SR bug fix

into  perch.ndb.mysql.com:/home/jonas/src/50-work

  Fix monster SR bug making SR with ordered indexes (or temporary tables) broken

into  mysql.com:/windows/Linux_space/MySQL/mysql-5.1-new-ndb

into  mysql.com:/windows/Linux_space/MySQL/mysql-5.1-new-ndb

Bug #21072  Duplicate key error in NDB references wrong key: use MAX_KEY to signal unknown key: Added string initialization

into  mysql.com:/windows/Linux_space/MySQL/mysql-5.1

into  mysql.com:/windows/Linux_space/MySQL/mysql-5.0

Bug #21072  Duplicate key error in NDB references wrong key: use MAX_KEY to signal unknown key: Added string initialization

into  orca.ndb.mysql.com:/export/home/space/pekka/ndb/version/my51-tux

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

  and use it for testOperations/testTransactions

  fix another incorrect assertion

  Dont assert when getting gci=0 in read only transaction

into  perch.ndb.mysql.com:/home/jonas/src/51-work

  this changes lock taken during peek, to decrease likelyhood of transaction abort
  

into  perch.ndb.mysql.com:/home/jonas/src/50-work

  make sure not to release log buffer twice (or several times) in case of abort of multi update

  Make sure postExecute is not run for blobs if AO_IgnoreError

into  mysql.com:/windows/Linux_space/MySQL/mysql-5.1-new-ndb

update partition engine for handler::info returning int

into  willster.(none):/home/stewart/Documents/MySQL/5.1/bug19914-mk2-merge

into  mysql.com:/windows/Linux_space/MySQL/mysql-5.1-new-ndb

into  willster.(none):/home/stewart/Documents/MySQL/5.1/bug19914-mk2-merge

into  willster.(none):/home/stewart/Documents/MySQL/5.1/bug21253

Early abort, failing to allocate buffers, would go down the abort track and
 end up trying to sendDropTriggers (as the standard stop backup does). 
However, it is possible to not have any tables yet defined in the backup 
(due to allocating buffers is before this). Simple check in sendDropTrig 
(and continue to next step). Files may be open, so we continue to close them.

Also updated ERROR_Codes (and added one to test this bug).