into  mysql.com:/home/psergey/mysql-5.1-bug8804-r12-merge

into  mysql.com:/home/psergey/mysql-5.0-bug8804-r12

Fixed typo problem that surfaced after the merge

into  mysql.com:/home/psergey/mysql-5.1-bug8804-r12-merge

identical pushed_cond_guards arrays. Allocate only one always.

into  mysql.com:/home/psergey/mysql-5.0-bug8804-r12

into  mysql.com:/home/gluh/MySQL/Merge/5.1-opt

into  mysql.com:/home/gluh/MySQL/Merge/5.1-opt

into  mysql.com:/home/gluh/MySQL/Merge/5.0-opt

into  macbook.gmz:/Users/kgeorge/mysql/work/merge-5.1-opt

geometry dependent parts moved to proper .test files

into  willster.(none):/home/stewart/Documents/MySQL/5.0/ndb-work

into  willster.(none):/home/stewart/Documents/MySQL/5.1/ndb-work

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

into  olga.mysql.com:/home/igor/mysql-5.0-opt

into  olga.mysql.com:/home/igor/mysql-5.0-opt

into  rakia.gmz:/home/kgeorge/mysql/autopush/B6172-5.1-opt

 RAND() must accept scalar expressions regardless of their kind.
 That includes both constant expressions and expressions that 
 depend on column values.
 When the expression is constant the random seed can be initialized
 at compile time.
 However when the expression is not constant the random seed must be
 initialized at each invocation (while it still can be allocated at
 compile time).
 Implemented the above rules by extending Item_func_rand::val_real()
 to initialize the random seed at the correct place.

into  clam.ndb.mysql.com:/export/space/pekka/ndb/version/my50-ndb

into  clam.ndb.mysql.com:/export/space/pekka/ndb/version/my51-ndb

into  willster.(none):/home/stewart/Documents/MySQL/5.0/bug25487

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

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

into  clam.ndb.mysql.com:/export/space/pekka/ndb/version/my51-ndb

into  macbook.gmz:/Users/kgeorge/mysql/work/merge-5.1-opt

into  mysql.com:/home/gluh/MySQL/Merge/5.0-opt

  
  aim is to:
  a) if set_connect_timeout called, timeout connect attempt (for retry on
  next call) after timeout period
  b) preserve existing blocking behaviour otherwise (for, e.g. mgmapi)
  
  Related to customer issue with long time deleting ndb_cluster_connection
  object. believe we're hanging on the connect(2) call until timeout (when
  we then realise we should exit the thread).

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

    Fix bug in event handling wrt early node shutdown

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

- post review changes

The bug is actually a duplicate of the bug 14708.
Down-ported the fix for 14708 from 5.0.  
Merged the test case for bug 14708 from 5.0.