Oracle 5.0 Reference Manual page 1547

• Temporary errors.
Temporary failure, distribution changed
• Errors due to node failure.
different node failure errors. (However, there should be no aborted transactions when performing a
planned shutdown of the cluster.)
In either of these cases, any errors that are generated must be handled within the application. This
should be done by retrying the transaction.
See also Section 17.1.5.2, "Limits and Differences of MySQL Cluster from Standard MySQL
17.1.5.5. Limits Associated with Database Objects in MySQL Cluster
Some database objects such as tables and indexes have different limitations when using the
NDBCLUSTER
• Identifiers.
as when using other table handlers. Attribute names are truncated to 31 characters, and if not unique
after truncation give rise to errors. Database names and table names can total a maximum of 122
characters. In other words, the maximum length for an
number of characters in the name of the database of which that table is a part.
• Table names containing special characters.
than letters, numbers, dashes, and underscores and which are created on one SQL node may not be
discovered correctly by other SQL nodes. (Bug #31470)
• Number of tables and other database objects.
database in MySQL 5.0 is limited to 1792. The maximum number of all
objects in a single MySQL Cluster—including databases, tables, and indexes—is limited to 20320.
• Attributes per table.
is limited to 128.
• Attributes per key.
• Row size.
column contributes 256 + 8 = 264 bytes to this total.
• Number of rows per partition.
MySQL Cluster partition varies with the number of replicas times the number of fragments. Since
the number of partitions is the same as the number of data nodes in the cluster (see
"MySQL Cluster Nodes, Node Groups, Replicas, and
fragments—and thus the available space—by using more data nodes.
17.1.5.6. Unsupported or Missing Features in MySQL Cluster
A number of features supported by other storage engines are not supported for
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.
• Index prefixes.
as part of an index specification in a statement such as
INDEX, the prefix is ignored.
•
OPTIMIZE
•
LOAD TABLE ... FROM
• Savepoints and rollbacks.
Known Limitations of MySQL Cluster
When first starting a node, it is possible that you may see Error 1204
The stopping or failure of any data node can result in a number of
storage engine:
Database names, table names and attribute names cannot be as long in
The maximum number of attributes (that is, columns and indexes) per table
The maximum number of attributes per key is 32.
The maximum permitted size of any one row is 8052 bytes. Each
The foreign key construct is ignored, just as it is in
Prefixes on indexes are not supported for
operations.
OPTIMIZE
MASTER.
Savepoints and rollbacks to savepoints are ignored as in MyISAM.
and similar temporary errors.
NDB
tables whose names contain characters other
NDB
The maximum number of tables in a Cluster
The maximum number of rows that can be stored in a single
Partitions"), you can increase the number of
CREATE
operations are not supported.
LOAD TABLE ... FROM MASTER
1527
table name is 122 characters, less the
NDBCLUSTER
BLOB
NDB
MyISAM
tables. If a prefix is used
NDBCLUSTER
TABLE, or
TABLE, ALTER
is not supported.
Limits".
tables
NDB
database
or
TEXT
Section 17.1.2,
tables. Trying to
tables.
CREATE