bk commit into 5.1 tree (tomas:1.2414)

[tomas]

Below is the list of changes that have just been committed into a local
5.1 repository of tomas. When tomas does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://dev.mysql.com/doc/mysql/en/installing-source-tree.html

ChangeSet
  1.2414 07/02/12 14:49:17 tomas@stripped +1 -0
  unpdate cluster change history

  cluster_change_hist.txt
    1.6 07/02/12 14:49:09 tomas@stripped +33 -21
    unpdate cluster change history

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	tomas
# Host:	poseidon.mysql.com
# Root:	/home/tomas/mysql-5.1-telco-6.1_2

--- 1.5/cluster_change_hist.txt	2007-01-31 16:21:08 +07:00
+++ 1.6/cluster_change_hist.txt	2007-02-12 14:49:09 +07:00
@@ -1,29 +1,41 @@
 
-mysql-5.1.15-ndb-6.1.1
-  - valgrind leak - no injected events if operation is not connected
-  - bug#25794 - Delete+Read (in same op) crashes datanodes if >5 cols or disk/varchar
-  - bug#25286 - NDB data node crashed in DBLQH, Line 2483
-  - Fix so that node version is recomputed at node failure
-  - added extra version info to API to enable support for non-supported online
-    software upgrade
-  - 255 api support
+mysql-5.1.15-ndb-6.1.2 (7 Feb 2007)
+
+  Bug #26267 - using node ids > 48 causes invalid memory access
+
+---------------------------------------------------
+
+mysql-5.1.15-ndb-6.1.1 (31 Jan 2007)
+
+  Bug #25997 - Valgrind reports leak in event code in mysqld during hadeling of NF and CF
+  Bug #25794 - Delete+Read (in same op) crashes datanodes if >5 cols or disk/varchar
+  Bug #25286 - NDB data node crashed in DBLQH, Line 2483
+
+  (* added extra version info to API to enable support for non-supported online software upgrade)
+  * 255 node support
+
+  Notes:
+
+  - This release is not online upgradable with ndb-6.1.0.
+  - All executables needs to be replaced
+  - All ndbapi/mgmapi application should be recompiled
 
 ---------------------------------------------------
 
-mysql-5.1.14-ndb-6.1.0 
+mysql-5.1.14-ndb-6.1.0 (20 Dec 2006)
 
-  bug#25059 - Unique index lookup execute(Commit) on non existing tuple can lead to 4012
-  bug#25090 - Incorrect handling of execute(Commit, AO_IgnoreError), can lead to DBCT crash
-  bug#19956 - Problems with VARCHAR primary key and BLOB fields
-  bug#24949 - Pulling cable from _last_ db-node can cause 6min timeout in api
-  bug#25001 - MEDIUMTEXT column not stored on disk
-  bug#24664 - Rare problem in LCP, can lead to unability to restart
-  bug#24917 - Makeing node restart with "newly" dropped disk table can cause failure during restart
-  bug#24914 - Start Transaction with hint guessed incorrectly
-  bug#21948 - Repeated create/drop/truncate(DD) together with restarts can cause SR failure
-  bug#17605 - DD Extents are not available until after LCP
-  bug#22773 - NDB_LE_Connected sent when it should be NDB_LE_Disconnected
-  bug#24166 - SR-crash if DD and hidden key
+  Bug #25059 - Unique index lookup execute(Commit) on non existing tuple can lead to 4012
+  Bug #25090 - Incorrect handling of execute(Commit, AO_IgnoreError), can lead to DBCT crash
+  Bug #19956 - Problems with VARCHAR primary key and BLOB fields
+  Bug #24949 - Pulling cable from _last_ db-node can cause 6min timeout in api
+  Bug #25001 - MEDIUMTEXT column not stored on disk
+  Bug #24664 - Rare problem in LCP, can lead to unability to restart
+  Bug #24917 - Makeing node restart with "newly" dropped disk table can cause failure during restart
+  Bug #24914 - Start Transaction with hint guessed incorrectly
+  Bug #21948 - Repeated create/drop/truncate(DD) together with restarts can cause SR failure
+  Bug #17605 - DD Extents are not available until after LCP
+  Bug #22773 - NDB_LE_Connected sent when it should be NDB_LE_Disconnected
+  Bug #24166 - SR-crash if DD and hidden key
 
   * add support for periodic mem-reporting, config.ini parameter "MemReportFrequency" which is specified in seconds