Author: jstephens
Date: 2006-03-29 12:59:44 +0200 (Wed, 29 Mar 2006)
New Revision: 1699
Log:
A Cluster table can't have an AUTO_INCREMENT column that is not the table's PK.
(Fixes Docs bug #17190)
Modified:
trunk/refman-4.1/ndbcluster.xml
trunk/refman-5.0/ndbcluster.xml
trunk/refman-5.1/ndbcluster.xml
Modified: trunk/refman-4.1/ndbcluster.xml
===================================================================
--- trunk/refman-4.1/ndbcluster.xml 2006-03-29 08:06:32 UTC (rev 1698)
+++ trunk/refman-4.1/ndbcluster.xml 2006-03-29 10:59:44 UTC (rev 1699)
@@ -9183,6 +9183,31 @@
'<replaceable>tbl_name</replaceable>'</errortext>.
</para>
</listitem>
+
+ <listitem>
+ <para>
+ Like other MySQL storage engines, the
+ <literal>NDB</literal> storage engine can handle a
+ maximum of one <literal>AUTO_INCREMENT</literal>
+ column per table. However, in the case of a Cluster
+ table with no explicit primary key, an
+ <literal>AUTO_INCREMENT</literal> column is
+ automatically defined and used as a
+ <quote>hidden</quote> primary key. For this reason,
+ you cannot define a table that has an explicit
+ <literal>AUTO_INCREMENT</literal> column unless that
+ column is also declared using the <literal>PRIMARY
+ KEY</literal> option.
+ </para>
+
+ <para>
+ Attempting to create a table with an
+ <literal>AUTO_INCREMENT</literal> column that is not
+ the table's primary key, and using the
+ <literal>NDB</literal> storage engine, fails with an
+ error.
+ </para>
+ </listitem>
</itemizedlist>
</listitem>
Modified: trunk/refman-5.0/ndbcluster.xml
===================================================================
--- trunk/refman-5.0/ndbcluster.xml 2006-03-29 08:06:32 UTC (rev 1698)
+++ trunk/refman-5.0/ndbcluster.xml 2006-03-29 10:59:44 UTC (rev 1699)
@@ -9168,6 +9168,31 @@
'<replaceable>tbl_name</replaceable>'</errortext>.
</para>
</listitem>
+
+ <listitem>
+ <para>
+ Like other MySQL storage engines, the
+ <literal>NDB</literal> storage engine can handle a
+ maximum of one <literal>AUTO_INCREMENT</literal>
+ column per table. However, in the case of a Cluster
+ table with no explicit primary key, an
+ <literal>AUTO_INCREMENT</literal> column is
+ automatically defined and used as a
+ <quote>hidden</quote> primary key. For this reason,
+ you cannot define a table that has an explicit
+ <literal>AUTO_INCREMENT</literal> column unless that
+ column is also declared using the <literal>PRIMARY
+ KEY</literal> option.
+ </para>
+
+ <para>
+ Attempting to create a table with an
+ <literal>AUTO_INCREMENT</literal> column that is not
+ the table's primary key, and using the
+ <literal>NDB</literal> storage engine, fails with an
+ error.
+ </para>
+ </listitem>
</itemizedlist>
</listitem>
Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml 2006-03-29 08:06:32 UTC (rev 1698)
+++ trunk/refman-5.1/ndbcluster.xml 2006-03-29 10:59:44 UTC (rev 1699)
@@ -11202,6 +11202,31 @@
'<replaceable>tbl_name</replaceable>'</errortext>.
</para>
</listitem>
+
+ <listitem>
+ <para>
+ Like other MySQL storage engines, the
+ <literal>NDB</literal> storage engine can handle a
+ maximum of one <literal>AUTO_INCREMENT</literal>
+ column per table. However, in the case of a Cluster
+ table with no explicit primary key, an
+ <literal>AUTO_INCREMENT</literal> column is
+ automatically defined and used as a
+ <quote>hidden</quote> primary key. For this reason,
+ you cannot define a table that has an explicit
+ <literal>AUTO_INCREMENT</literal> column unless that
+ column is also declared using the <literal>PRIMARY
+ KEY</literal> option.
+ </para>
+
+ <para>
+ Attempting to create a table with an
+ <literal>AUTO_INCREMENT</literal> column that is not
+ the table's primary key, and using the
+ <literal>NDB</literal> storage engine, fails with an
+ error.
+ </para>
+ </listitem>
</itemizedlist>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1699 - in trunk: refman-4.1 refman-5.0 refman-5.1 | jon | 29 Mar |
