Oracle 5.0 Reference Manual page 1544

and used as a "hidden" primary key. For this reason, you cannot define a table that has an explicit
AUTO_INCREMENT
Attempting to create a table with an
and using the
• MySQL Cluster and geometry data types.
Geometry data types
indexes are not supported.
17.1.5.2. Limits and Differences of MySQL Cluster from Standard MySQL Limits
In this section, we list limits found in MySQL Cluster that either differ from limits found in, or that are not
found in, standard MySQL.
Memory usage and recovery.
automatically recovered when deleted, as it is with other storage engines. Instead, the following rules
hold true:
• A
DELETE
available for re-use by inserts on the same table only. However, this memory can be made available
for general re-use by performing a rolling restart of the cluster. See
Rolling Restart of a MySQL
• A
DROP TABLE
this table for re-use by any
• Limits imposed by the cluster's configuration.
A number of hard limits exist which are configurable, but available main memory in the cluster
sets limits. See the complete list of configuration parameters in
Configuration
include:
• Database memory size and index memory size
DataMemory
specific table; once allocated, this memory cannot be freed except by dropping the table.
See Section 17.3.2.5, "Defining MySQL Cluster Data
DataMemory
• The maximum number of operations that can be performed per transaction is set using the
configuration parameters
• Different limits related to tables and indexes. For example, the maximum number of ordered
indexes in the cluster is determined by MaxNoOfOrderedIndexes, and the maximum number of
ordered inexes per table is 16.
• Memory usage.
has one or more
space is required when using the
Known Limitations of MySQL Cluster
column unless that column is also declared using the
storage engine, fails with an error.
NDB
(WKT and WKB) are supported in
Memory consumed when data is inserted into an
statement on an table makes the memory formerly used by the deleted rows
NDB
Cluster".
or
TRUNCATE TABLE
table, either by the same table or by another
NDB
Note
Recall that
TRUNCATE TABLE
Section 13.1.21,
Files". Most configuration parameters can be upgraded online. These hard limits
is allocated as 32KB pages. As each
and IndexMemory.
MaxNoOfConcurrentOperations
Note
Bulk loading,
special cases by running multiple transactions, and so are not subject to
this limitation.
All Cluster table rows are of fixed length. This means (for example) that if a table
fields containing only relatively small values, more memory and disk
VARCHAR
AUTO_INCREMENT
NDB
operation on an
NDB
drops and re-creates the table. See
"TRUNCATE TABLE
(DataMemory
DataMemory
Nodes", for further information about
TABLE, and
TRUNCATE
storage engine than would be the case for the same table
NDB
1524
PRIMARY KEY
column that is not the table's primary key,
tables in MySQL 5.0. However, spatial
Section 17.5.5, "Performing a
table frees the memory that was used by
NDB
Syntax".
Section 17.3.2, "MySQL Cluster
and IndexMemory, respectively).
page is used, it is assigned to a
and MaxNoOfLocalOperations.
are handled as
ALTER TABLE
option.
table is not
NDB
table.