A number of features supported by other storage engines are not
NDB tables. Trying to
use any of these features in MySQL Cluster does not cause errors
in or of itself; however, errors may occur in applications that
expects the features to be supported or enforced:
Foreign key constraints.
Prior to MySQL Cluster NDB 7.3, the foreign key construct
is ignored, just as it is by
tables. Foreign keys are supported in MySQL Cluster NDB
7.3 and later.
Prefixes on indexes are not supported for
NDBCLUSTER tables. If a prefix is used
as part of an index specification in a statement such as
ALTER TABLE, or
CREATE INDEX, the prefix is
OPTIMIZE operations are not supported.
Beginning with MySQL Cluster NDB 6.3.7, this limitation has been lifted. See Section 3.6.11, “Previous MySQL Cluster Issues Resolved in MySQL 5.1, MySQL Cluster NDB 6.x, and MySQL Cluster NDB 7.x”, for more information.
LOAD TABLE ... FROM MASTER.
LOAD TABLE FROM MASTER is
Savepoints and rollbacks.
Savepoints and rollbacks to savepoints are ignored as in
Durability of commits. There are no durable commits on disk. Commits are replicated, but there is no guarantee that logs are flushed to disk on commit.
Statement-based replication is not supported. Use
setting up cluster replication. See
Chapter 8, MySQL Cluster Replication, for more
See Section 3.6.3, “Limits Relating to Transaction Handling in MySQL Cluster”,
for more information relating to limitations on transaction