A number of features supported by other storage engines are not
supported for 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.
The foreign key construct is ignored, just as it is in
MyISAM
tables.
Index prefixes.
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
CREATE TABLE
,
ALTER TABLE
, or
CREATE INDEX
, the prefix is
ignored.
OPTIMIZE
operations.
OPTIMIZE
operations are not supported.
Beginning with MySQL Cluster NDB 6.3.7, this limitation has been lifted. See Section 17.1.5.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 not
supported.
Savepoints and rollbacks.
Savepoints and rollbacks to savepoints are ignored as in
MyISAM
.
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.
Replication.
Statement-based replication is not supported. Use
--binlog-format=ROW
(or
--binlog-format=MIXED
) when
setting up cluster replication. See
Section 17.6, “MySQL Cluster Replication”, for more
information.
InnoDB
plugin not supported.
Currently, MySQL Cluster is not compatible with the
InnoDB Plugin
. You must use the version
of InnoDB
that is supplied
with the MySQL Server. See
Section 17.2.1, “MySQL Cluster Multi-Computer Installation”, for
information about enabling
InnoDB
storage engine support
with MySQL Cluster.
See Section 17.1.5.3, “Limits Relating to Transaction Handling in MySQL Cluster”,
for more information relating to limitations on transaction
handling in NDB
.
User Comments
Add your own comment.