Author: js221926
Date: 2011-06-28 09:09:02 +0200 (Tue, 28 Jun 2011)
New Revision: 26631
Log:
Make it abundantly clear that STORAGE and COLUMN_FORMAT keywords are:
(a) supported in Cluster only
(b) not recognised (and thus cause a syntax error) in any other version of mysqld
Ref. BUG#61552
Modified:
trunk/refman-5.1/sql-syntax-data-definition.xml
Modified: trunk/refman-5.1/sql-syntax-data-definition.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-data-definition.xml 2011-06-28 06:36:05 UTC (rev 26630)
+++ trunk/refman-5.1/sql-syntax-data-definition.xml 2011-06-28 07:09:02 UTC (rev 26631)
Changed blocks: 4, Lines Added: 35, Lines Deleted: 13; 3868 bytes
@@ -2288,6 +2288,17 @@
option did not work correctly. (Bug#42549)
</para>
+ <note>
+ <para>
+ The <literal>STORAGE</literal> and
+ <literal>COLUMN_FORMAT</literal> keywords are supported only
+ in MySQL Cluster; in any other version of MySQL, attempting to
+ use either of these keywords in a <literal role="stmt">CREATE
+ TABLE</literal> or <literal>ALTER TABLE</literal> statement
+ results in an error.
+ </para>
+ </note>
+
<para>
Online operations are noncopying; that is, they do not require
that indexes be re-created. They do not lock the table being
@@ -5777,17 +5788,18 @@
<primary>column format</primary>
</indexterm>
- Beginning with MySQL Cluster NDB 6.2.5 and MySQL Cluster NDB
- 6.3.2, it is also possible to specify a data storage format
- for individual columns of <literal role="se">NDB</literal>
- tables using <literal>COLUMN_FORMAT</literal>. Permissible
- column formats are <literal>FIXED</literal>,
- <literal>DYNAMIC</literal>, and <literal>DEFAULT</literal>.
- <literal>FIXED</literal> is used to specify fixed-width
- storage, <literal>DYNAMIC</literal> permits the column to be
- variable-width, and <literal>DEFAULT</literal> causes the
- column to use fixed-width or variable-width storage as
- determined by the column's data type (possibly overridden by a
+ In MySQL Cluster—beginning with MySQL Cluster NDB 6.2.5
+ and MySQL Cluster NDB 6.3.2—it is also possible to
+ specify a data storage format for individual columns of
+ <literal role="se">NDB</literal> tables using
+ <literal>COLUMN_FORMAT</literal>. Permissible column formats
+ are <literal>FIXED</literal>, <literal>DYNAMIC</literal>, and
+ <literal>DEFAULT</literal>. <literal>FIXED</literal> is used
+ to specify fixed-width storage, <literal>DYNAMIC</literal>
+ permits the column to be variable-width, and
+ <literal>DEFAULT</literal> causes the column to use
+ fixed-width or variable-width storage as determined by the
+ column's data type (possibly overridden by a
<literal>ROW_FORMAT</literal> specifier).
</para>
@@ -5800,7 +5812,12 @@
<para>
<literal>COLUMN_FORMAT</literal> currently has no effect on
columns of tables using storage engines other than
- <literal role="se">NDB</literal>.
+ <literal role="se">NDB</literal>. The
+ <literal>COLUMN_FORMAT</literal> keyword is supported only in
+ the build of <command>mysqld</command> that is supplied with
+ MySQL Cluster; it is not recognized in any other version of
+ MySQL, where attempting to use
+ <literal>COLUMN_FORMAT</literal> causes a syntax error.
</para>
</listitem>
@@ -5844,7 +5861,12 @@
<para>
The <literal>STORAGE</literal> clause has no effect on tables
using storage engines other than
- <literal role="se">NDB</literal>.
+ <literal role="se">NDB</literal>. The
+ <literal>STORAGE</literal> keyword is supported only in the
+ build of <command>mysqld</command> that is supplied with MySQL
+ Cluster; it is not recognized in any other version of MySQL,
+ where any attempt to use the <literal>STORAGE</literal>
+ keyword causes a syntax error.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@oter02: r26631 - trunk/refman-5.1 | jon.stephens | 28 Jun |