Some SQL statements relating to certain MySQL features produce
errors when used with
as described in the following list:
Temporary tables. Temporary tables are not supported. Trying either to create a temporary table that uses the
NDBstorage engine or to alter an existing temporary table to use
NDBfails with the error Table storage engine 'ndbcluster' does not support the create option 'TEMPORARY'.
Indexes and keys in NDB tables. Keys and indexes on NDB Cluster tables are subject to the following limitations:
Column width. Attempting to create an index on an
NDBtable column whose width is greater than 3072 bytes succeeds, but only the first 3072 bytes are actually used for the index. In such cases, a warning Specified key was too long; max key length is 3072 bytes is issued, and a
SHOW CREATE TABLEstatement shows the length of the index as 3072.
USING HASH keys and NULL. Using nullable columns in unique keys and primary keys means that queries using these columns are handled as full table scans. To work around this issue, make the column
NOT NULL, or re-create the index without the
Prefixes. There are no prefix indexes; only entire columns can be indexed. (The size of an
NDBcolumn index is always the same as the width of the column in bytes, up to and including 3072 bytes, as described earlier in this section. Also see Section 3.7.6, “Unsupported or Missing Features in NDB Cluster”, for additional information.)
BIT columns. A
BITcolumn cannot be a primary key, unique key, or index, nor can it be part of a composite primary key, unique key, or index.
AUTO_INCREMENT columns. Like other MySQL storage engines, the
NDBstorage engine can handle a maximum of one
AUTO_INCREMENTcolumn per table, and this column must be indexed. However, in the case of an NDB table with no explicit primary key, an
AUTO_INCREMENTcolumn is automatically defined and used as a “hidden” primary key. For this reason, you cannot create an
NDBtable having an
AUTO_INCREMENTcolumn and no explicit primary key.
Restrictions on foreign keys. Support for foreign key constraints in NDB Cluster 7.3 and 7.4 is comparable to that provided by
InnoDB, subject to the following restrictions:
Every column referenced as a foreign key requires an explicit unique key, if it is not the table's primary key.
ON UPDATE CASCADEis not supported when the reference is to the parent table's primary key.
This is because an update of a primary key is implemented as a delete of the old row (containing the old primary key) plus an insert of the new row (with a new primary key). This is not visible to the
NDBkernel, which views these two rows as being the same, and thus has no way of knowing that this update should be cascaded.
SET DEFAULTis not supported. (Also not supported by
NO ACTIONkeywords are accepted but treated as
RESTRICT. (Also the same as with
Prior to NDB 7.3.5, when creating a table with foreign key referencing an index in another table, it sometimes appeared possible to create the foreign key even if the order of the columns in the indexes did not match, due to the fact that an appropriate error was not always returned internally. A partial fix for this issue in NDB 7.3.5 improves the error used internally to work in most cases; however, it is still possible for this situation to occur in the event that the parent index is a unique index. (Bug #18094360)
In NDB 7.3, when adding or dropping a foreign key using
ALTER TABLE, the parent table's metadata is not updated, which makes it possible subsequently to execute
ALTER TABLEstatements on the parent that should be invalid. This issue also affects NDB 7.4 releases prior to 7.4.15. To work around this issue, execute
SHOW CREATE TABLEon the parent table immediately after adding or dropping the foreign key; this forces the parent's metadata to be reloaded.
This issue is fixed in NDB 7.4.15 and later. (Bug #82989, Bug #24666177)
NDB Cluster and geometry data types. Geometry data types (
WKB) are supported for
NDBtables. However, spatial indexes are not supported.
Character sets and binary log files. Currently, the
ndb_binlog_indextables are created using the
latin1(ASCII) character set. Because names of binary logs are recorded in this table, binary log files named using non-Latin characters are not referenced correctly in these tables. This is a known issue, which we are working to fix. (Bug #50226)
Creating NDB tables with user-defined partitioning. Support for user-defined partitioning in NDB Cluster is restricted to [
KEYpartitioning. Using any other partitioning type with
CREATE TABLEstatement results in an error.
It is possible to override this restriction, but doing so is not supported for use in production settings. For details, see User-defined partitioning and the NDB storage engine (NDB Cluster).
Default partitioning scheme. All NDB Cluster tables are by default partitioned by
KEYusing the table's primary key as the partitioning key. If no primary key is explicitly set for the table, the “hidden” primary key automatically created by the
NDBstorage engine is used instead. For additional discussion of these and related issues, see KEY Partitioning.
The table must have an explicit primary key.
All columns listed in the table's partitioning expression must be part of the primary key.
Exception. If a user-partitioned
NDBCLUSTERtable is created using an empty column-list (that is, using
PARTITION BY [LINEAR] KEY()), then no explicit primary key is required.
Maximum number of partitions for NDBCLUSTER tables. The maximum number of partitions that can defined for a
NDBCLUSTERtable when employing user-defined partitioning is 8 per node group. (See Section 3.2, “NDB Cluster Nodes, Node Groups, Replicas, and Partitions”, for more information about NDB Cluster node groups.
DROP PARTITION not supported. It is not possible to drop partitions from
ALTER TABLE ... DROP PARTITION. The other partitioning extensions to
REORGANIZE PARTITION, and
COALESCE PARTITION—are supported for NDB tables, but use copying and so are not optimized. See Management of RANGE and LIST Partitions and ALTER TABLE Syntax.