The following Cluster limitations in MySQL 4.1 have been resolved in MySQL 5.0 as shown below:
Character set support.
NDBCLUSTER storage engine
supports all character sets and collations available in
Character set directory.
Beginning with MySQL 5.0.21, it is possible to install
MySQL with Cluster support to a nondefault location and
change the search path for font description files using
options. (Previously, ndbd in MySQL 5.0
searched only the default path—typically
Metadata objects. Prior to MySQL 5.0.6, the maximum number of metadata objects possible was 1600. Beginning with MySQL 5.0.6, this limit is increased to 20320.
Query cache. Unlike the case in MySQL 4.1, the Cluster storage engine in MySQL 5.0 supports MySQL's query cache. See Section 8.6.3, “The MySQL Query Cache”.
In MySQL 5.0.19 and earlier,
UPDATE IGNORE, and
REPLACE were supported only
for primary keys, but not for unique keys. It was possible
to work around this issue by removing the constraint, then
dropping the unique index, performing any inserts, and
then adding the unique index again.