Some SQL statements relating to certain MySQL features produce
errors when used with
as described in the following list:
Temporary tables are not supported. Trying either to
create a temporary table that uses the
NDB storage engine or to
alter an existing temporary table to use
NDB fails with the error
Table storage engine 'ndbcluster' does not
support the create option 'TEMPORARY'.
Indexes and keys in
Keys and indexes on MySQL Cluster tables are subject to
the following limitations:
Attempting to create an index on an
NDB table 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
TABLE statement shows the length of the
index as 3072.
NDB storage engine
does not support
which are possible for
There are no prefix indexes; only entire columns can
be indexed. (The size of an
column 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 126.96.36.199, “Unsupported or Missing Features in MySQL Cluster”,
for additional information.)
BIT column cannot be
a primary key, unique key, or index, nor can it be
part of a composite primary key, unique key, or index.
Like other MySQL storage engines, the
NDB storage engine can
handle a maximum of one
AUTO_INCREMENT column per table.
However, in the case of a Cluster table with no
explicit primary key, an
AUTO_INCREMENT column is
automatically defined and used as a
“hidden” primary key. For this reason,
you cannot define a table that has an explicit
AUTO_INCREMENT column unless that
column is also declared using the
KEY option. Attempting to create a table
AUTO_INCREMENT column that
is not the table's primary key, and using the
NDB storage engine, fails
with an error.
MySQL Cluster and geometry data types.
Geometry data types (
WKB) are supported in
NDB tables in MySQL
4.1. However, spatial indexes are not
Character set support. Not all charsets and collations are supported. For a list of those that are supported, see http://dev.mysql.com/doc/relnotes/mysql-cluster/4.1/en/mysql-cluster-news-4-1-6.html.
Character set directory.
ndbd searches only the default path
for character sets. Thus, it is not possible to install
MySQL with Cluster support in a different path (in the
case of the
.tar.gz archives, other
/usr/local/mysql) if character
sets that are not compiled into the MySQL Server need to