Skip navigation links

Additional languages
15.12.2 Limits and Differences from Standard MySQL Limits »
Section Navigation      [Toggle]

15.12.1. Non-Compliance In SQL Syntax

Some SQL statements relating to certain MySQL features produce errors when used with NDB tables, as described in the following list:

  • Temporary tables.  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 NDB tables.  Keys and indexes on MySQL Cluster tables are subject to the following limitations:

    • TEXT and BLOB columns.  You cannot create indexes on NDB table columns that use any of the TEXT or BLOB data types.

    • FULLTEXT indexes.  The NDB storage engine does not support FULLTEXT indexes, which are possible for MyISAM tables only.

      However, you can create indexes on VARCHAR columns of NDB tables.

    • There are no prefix indexes; only entire fields can be indexed.

    • BIT columns.  A 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.

    • AUTO_INCREMENT columns.  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 PRIMARY KEY option. Attempting to create a table with an 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 datatypes (WKT and WKB) are supported in NDB tables in MySQL 4.1. However, spatial indexes are not supported.

  • Character set support.  Not all charsets and collations are supported; see Section B.5.14, “Changes in MySQL Cluster-4.1.6 (10 October 2004)”, for a list of those that are supported.

    Character set directory.  ndbd searches only the default path (typically /usr/local/mysql/share/mysql/charsets) 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 than /usr/local/mysql) if character sets that are not compiled into the MySQL Server need to be used.

  • Row-based replication.  When using row-based replication with MySQL Cluster, binary logging cannot be disabled. That is, the NDB storage engine ignores the value of SQL_LOG_BIN. (Bug#16680)

  • auto_increment_increment and auto_increment_offset.  The auto_increment_increment and auto_increment_offset server system variables are not supported for Cluster replication.