Changes in MySQL Cluster NDB 7.0.12 (5.1.41-ndb-7.0.12) (2010-02-03)

Note

MySQL Cluster NDB 7.0.12 was withdrawn shortly after release,
due to Bug #51027. Users of the original 7.0.12 release should
upgrade to MySQL Cluster NDB 7.0.12b, which fixes this issue
(and others). Users of MySQL Cluster NDB 7.0.11 or MySQL
Cluster NDB 7.0.11a should upgrade to MySQL Cluster NDB
7.0.11b, if they have not done so already.

This is a testing release only, for the purpose of testing the
fix for Bug #49190. This release is otherwise identical to MySQL
Cluster NDB 7.0.11b; users of MySQL Cluster NDB 7.0.11 or MySQL
Cluster NDB 7.0.11a who are not interested in testing this
change should upgrade to MySQL Cluster NDB 7.0.11b (if they have
not done so already), then wait until MySQL Cluster NDB 7.0.13
becomes available.

This release also incorporates all bugfixes and changes made in
previous MySQL Cluster releases, as well as all bugfixes and
feature changes which were added in mainline MySQL 5.1 through
MySQL 5.1.41 (see Changes in MySQL 5.1.41 (2009-11-05)).

Note

Please refer to our bug database at
http://bugs.mysql.com/ for more details about
the individual bugs fixed in this version.

Functionality Added or Changed

Numeric codes used in management server status update messages
in the cluster logs have been replaced with text descriptions.
(Bug #49627)

When a primary key lookup on an NDB
table containing one or more BLOB
columns was executed in a transaction, a shared lock on any blob
tables used by the NDB table was
held for the duration of the transaction. (This did not occur
for indexed or non-indexed WHERE conditions.)

Now in such cases, the lock is released after all
BLOB data has been read.
(Bug #49190)