Author: jstephens
Date: 2007-07-27 13:15:10 +0200 (Fri, 27 Jul 2007)
New Revision: 7251
Log:
Added undocumented options for CREATE LOGFILE GROUP, CREATE TABLESPACE,
ALTER LOGFILE GROUP, ALTER TABLESPACE.
Fixes Docs Bug #29530
Modified:
trunk/refman-5.1/sql-syntax.xml
trunk/refman-5.2/sql-syntax.xml
Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml 2007-07-27 10:03:03 UTC (rev 7250)
+++ trunk/refman-5.1/sql-syntax.xml 2007-07-27 11:15:10 UTC (rev 7251)
Changed blocks: 8, Lines Added: 41, Lines Deleted: 5; 4113 bytes
@@ -167,6 +167,7 @@
ALTER LOGFILE GROUP <replaceable>logfile_group</replaceable>
ADD UNDOFILE '<replaceable>file</replaceable>'
[INITIAL_SIZE [=] <replaceable>size</replaceable>]
+ [WAIT]
ENGINE [=] <replaceable>engine</replaceable>
</programlisting>
@@ -192,6 +193,12 @@
</para>
<para>
+ <literal>WAIT</literal> is parsed but otherwise ignored, and so
+ has no effect in MySQL ¤t-series;. It is intended for
+ future expansion.
+ </para>
+
+ <para>
The <literal>ENGINE</literal> parameter (required) determines
the storage engine which is used by this log file group, with
<replaceable>engine</replaceable> being the name of the storage
@@ -1538,13 +1545,10 @@
<programlisting>
ALTER TABLESPACE <replaceable>tablespace</replaceable>
- ADD DATAFILE '<replaceable>file</replaceable>'
+ {ADD|DROP} DATAFILE '<replaceable>file</replaceable>'
[INITIAL_SIZE [=] <replaceable>size</replaceable>]
+ [WAIT]
ENGINE [=] <replaceable>engine</replaceable>
-
-ALTER TABLESPACE <replaceable>tablespace</replaceable>
- DROP DATAFILE '<replaceable>file</replaceable>'
- ENGINE [=] <replaceable>engine</replaceable>
</programlisting>
<para>
@@ -1590,6 +1594,12 @@
</para>
<para>
+ <literal>WAIT</literal> is parsed but otherwise ignored, and so
+ has no effect in MySQL ¤t-series;. It is intended for
+ future expansion.
+ </para>
+
+ <para>
When <literal>ALTER TABLESPACE ... ADD DATAFILE</literal> is
used with <literal>ENGINE = NDB</literal>, a data file is
created on each Cluster data node. You can verify that the data
@@ -2190,6 +2200,10 @@
ADD UNDOFILE '<replaceable>undo_file</replaceable>'
[INITIAL_SIZE [=] <replaceable>initial_size</replaceable>]
[UNDO_BUFFER_SIZE [=] <replaceable>undo_buffer_size</replaceable>]
+ [REDO_BUFFER_SIZE [=] <replaceable>redo_buffer_size</replaceable>]
+ [NODEGROUP [=] <replaceable>nodegroup_id</replaceable>]
+ [WAIT]
+ [COMMENT [=] <replaceable>comment_text</replaceable>]
ENGINE [=] <replaceable>engine_name</replaceable>
</programlisting>
@@ -2234,6 +2248,14 @@
</para>
<para>
+ <replaceable>REDO_BUFFER_SIZE</replaceable>,
+ <literal>NODEGROUP</literal>, <literal>WAIT</literal>, and
+ <literal>COMMENT</literal> are parsed but ignored, and so have
+ no effect in MySQL ¤t-series;. These options are intended
+ for future expansion.
+ </para>
+
+ <para>
When used with <literal>ENGINE [=] NDB</literal>, a log file
group and associated <literal>UNDO</literal> log file are
created on each Cluster data node. You can verify that the
@@ -4627,6 +4649,11 @@
USE LOGFILE GROUP <replaceable>logfile_group</replaceable>
[EXTENT_SIZE [=] <replaceable>extent_size</replaceable>]
[INITIAL_SIZE [=] <replaceable>initial_size</replaceable>]
+ [AUTOEXTEND_SIZE [=] <replaceable>autoextend_size</replaceable>]
+ [MAX_SIZE [=] <replaceable>max_size</replaceable>]
+ [NODEGROUP [=] <replaceable>nodegroup_id</replaceable>]
+ [WAIT]
+ [COMMENT [=] <replaceable>comment_text</replaceable>]
ENGINE [=] <replaceable>engine</replaceable>
</programlisting>
@@ -4711,6 +4738,15 @@
</para>
<para>
+ <replaceable>AUTOEXTEND_SIZE</replaceable>,
+ <literal>MAX_SIZE</literal>, <literal>NODEGROUP</literal>,
+ <literal>WAIT</literal>, and <literal>COMMENT</literal> are
+ parsed but ignored, and so have no effect in MySQL
+ ¤t-series;. These options are intended for future
+ expansion.
+ </para>
+
+ <para>
The <literal>ENGINE</literal> parameter determines the storage
engine which uses this tablespace, with
<replaceable>engine</replaceable> being the name of the storage
Modified: trunk/refman-5.2/sql-syntax.xml
===================================================================
--- trunk/refman-5.2/sql-syntax.xml 2007-07-27 10:03:03 UTC (rev 7250)
+++ trunk/refman-5.2/sql-syntax.xml 2007-07-27 11:15:10 UTC (rev 7251)
Changed blocks: 8, Lines Added: 41, Lines Deleted: 5; 4113 bytes
@@ -167,6 +167,7 @@
ALTER LOGFILE GROUP <replaceable>logfile_group</replaceable>
ADD UNDOFILE '<replaceable>file</replaceable>'
[INITIAL_SIZE [=] <replaceable>size</replaceable>]
+ [WAIT]
ENGINE [=] <replaceable>engine</replaceable>
</programlisting>
@@ -192,6 +193,12 @@
</para>
<para>
+ <literal>WAIT</literal> is parsed but otherwise ignored, and so
+ has no effect in MySQL ¤t-series;. It is intended for
+ future expansion.
+ </para>
+
+ <para>
The <literal>ENGINE</literal> parameter (required) determines
the storage engine which is used by this log file group, with
<replaceable>engine</replaceable> being the name of the storage
@@ -1538,13 +1545,10 @@
<programlisting>
ALTER TABLESPACE <replaceable>tablespace</replaceable>
- ADD DATAFILE '<replaceable>file</replaceable>'
+ {ADD|DROP} DATAFILE '<replaceable>file</replaceable>'
[INITIAL_SIZE [=] <replaceable>size</replaceable>]
+ [WAIT]
ENGINE [=] <replaceable>engine</replaceable>
-
-ALTER TABLESPACE <replaceable>tablespace</replaceable>
- DROP DATAFILE '<replaceable>file</replaceable>'
- ENGINE [=] <replaceable>engine</replaceable>
</programlisting>
<para>
@@ -1590,6 +1594,12 @@
</para>
<para>
+ <literal>WAIT</literal> is parsed but otherwise ignored, and so
+ has no effect in MySQL ¤t-series;. It is intended for
+ future expansion.
+ </para>
+
+ <para>
When <literal>ALTER TABLESPACE ... ADD DATAFILE</literal> is
used with <literal>ENGINE = NDB</literal>, a data file is
created on each Cluster data node. You can verify that the data
@@ -2198,6 +2208,10 @@
ADD UNDOFILE '<replaceable>undo_file</replaceable>'
[INITIAL_SIZE [=] <replaceable>initial_size</replaceable>]
[UNDO_BUFFER_SIZE [=] <replaceable>undo_buffer_size</replaceable>]
+ [REDO_BUFFER_SIZE [=] <replaceable>redo_buffer_size</replaceable>]
+ [NODEGROUP [=] <replaceable>nodegroup_id</replaceable>]
+ [WAIT]
+ [COMMENT [=] <replaceable>comment_text</replaceable>]
ENGINE [=] <replaceable>engine_name</replaceable>
</programlisting>
@@ -2242,6 +2256,14 @@
</para>
<para>
+ <replaceable>REDO_BUFFER_SIZE</replaceable>,
+ <literal>NODEGROUP</literal>, <literal>WAIT</literal>, and
+ <literal>COMMENT</literal> are parsed but ignored, and so have
+ no effect in MySQL ¤t-series;. These options are intended
+ for future expansion.
+ </para>
+
+ <para>
When used with <literal>ENGINE [=] NDB</literal>, a log file
group and associated <literal>UNDO</literal> log file are
created on each Cluster data node. You can verify that the
@@ -4634,6 +4656,11 @@
USE LOGFILE GROUP <replaceable>logfile_group</replaceable>
[EXTENT_SIZE [=] <replaceable>extent_size</replaceable>]
[INITIAL_SIZE [=] <replaceable>initial_size</replaceable>]
+ [AUTOEXTEND_SIZE [=] <replaceable>autoextend_size</replaceable>]
+ [MAX_SIZE [=] <replaceable>max_size</replaceable>]
+ [NODEGROUP [=] <replaceable>nodegroup_id</replaceable>]
+ [WAIT]
+ [COMMENT [=] <replaceable>comment_text</replaceable>]
ENGINE [=] <replaceable>engine</replaceable>
</programlisting>
@@ -4718,6 +4745,15 @@
</para>
<para>
+ <replaceable>AUTOEXTEND_SIZE</replaceable>,
+ <literal>MAX_SIZE</literal>, <literal>NODEGROUP</literal>,
+ <literal>WAIT</literal>, and <literal>COMMENT</literal> are
+ parsed but ignored, and so have no effect in MySQL
+ ¤t-series;. These options are intended for future
+ expansion.
+ </para>
+
+ <para>
The <literal>ENGINE</literal> parameter determines the storage
engine which uses this tablespace, with
<replaceable>engine</replaceable> being the name of the storage
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7251 - in trunk: refman-5.1 refman-5.2 | jon | 27 Jul |