Author: jstephens
Date: 2006-08-22 04:40:51 +0200 (Tue, 22 Aug 2006)
New Revision: 3078
Log:
Reformat
Modified:
trunk/refman-4.1/mysql-cluster.xml
trunk/refman-5.0/mysql-cluster.xml
trunk/refman-5.1/mysql-cluster.xml
trunk/refman-5.1/partitioning.xml
trunk/refman-5.1/sql-syntax.xml
Modified: trunk/refman-4.1/mysql-cluster.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster.xml 2006-08-22 02:38:35 UTC (rev 3077)
+++ trunk/refman-4.1/mysql-cluster.xml 2006-08-22 02:40:51 UTC (rev 3078)
Changed blocks: 10, Lines Added: 77, Lines Deleted: 66; 10765 bytes
@@ -7994,10 +7994,10 @@
<xref
linkend="mysql-cluster-configuration"/>.
</para>
-
+
<para>
- This section remains in development, and continues to be updated and
- expanded.
+ This section remains in development, and continues to be updated
+ and expanded.
</para>
<section id="mysql-cluster-rolling-restart">
@@ -8441,18 +8441,19 @@
</tr>
</tbody>
</table>
-
+
<para>
In the previous table, <emphasis role="bold">Stop</emphasis> and
- <emphasis role="bold">Start</emphasis> steps indicate that the process
- must be stopped completely using a shell command (such as
- <command>kill</command> on most Unix systems) or the management client
- <literal>STOP</literal> command, then started again from a system shell
- by invoking the <command>ndbd</command> or <command>ndb_mgmd</command>
- executable as appropriate. <emphasis role="bold">Restart</emphasis>
- indicates the process may be restarted using the
- <command>ndb_mgm</command> management client <literal>RESTART</literal>
- command.
+ <emphasis role="bold">Start</emphasis> steps indicate that the
+ process must be stopped completely using a shell command (such
+ as <command>kill</command> on most Unix systems) or the
+ management client <literal>STOP</literal> command, then started
+ again from a system shell by invoking the
+ <command>ndbd</command> or <command>ndb_mgmd</command>
+ executable as appropriate.
+ <emphasis role="bold">Restart</emphasis> indicates the process
+ may be restarted using the <command>ndb_mgm</command> management
+ client <literal>RESTART</literal> command.
</para>
</section>
@@ -9379,13 +9380,14 @@
section as of MySQL 4.1.8. Users of earlier MySQL Cluster
versions should note that some of these options have been
changed to make consistent with one another as well as with
- <command>mysqld</command>. You can use the <option>--help</option>
- option with any MySQL Cluster executable to view a list of the options
- which it supports.
+ <command>mysqld</command>. You can use the
+ <option>--help</option> option with any MySQL Cluster executable
+ to view a list of the options which it supports.
</para>
-
+
<para>
- The following options are common to all MySQL Cluster executables:
+ The following options are common to all MySQL Cluster
+ executables:
</para>
<itemizedlist>
@@ -9410,7 +9412,8 @@
<para>
<replaceable>connect_string</replaceable> sets the
connectstring to the management server as a command option.
- Available with <command>ndb_mgm</command> from MySQL 4.1.8 onward.
+ Available with <command>ndb_mgm</command> from MySQL 4.1.8
+ onward.
</para>
<programlisting>
@@ -9474,20 +9477,21 @@
<para>
<option>--version</option>, <option>-V</option>
</para>
-
+
<para>
- Prints the MySQL Cluster version number of the executable. The
- version number is relevant because not all versions can be used
- together, and the MySQL Cluster startup process verifies that the
- versions of the binaries being used can co-exist in the same
- cluster. This is also important when performing an online (rolling)
- software upgrade or downgrade of MySQL Cluster. (See
+ Prints the MySQL Cluster version number of the executable.
+ The version number is relevant because not all versions can
+ be used together, and the MySQL Cluster startup process
+ verifies that the versions of the binaries being used can
+ co-exist in the same cluster. This is also important when
+ performing an online (rolling) software upgrade or downgrade
+ of MySQL Cluster. (See
<xref linkend="mysql-cluster-rolling-restart"/>).
</para>
</listitem>
</itemizedlist>
-
+
<para>
The next few sections describe options specific to individual
<literal>NDB</literal> programs.
@@ -9703,7 +9707,7 @@
the execution engine until specifically requested to do so
by the management server. This can be accomplished by
issuing the proper <literal>START</literal> command in the
- management client (see
+ management client (see
<xref linkend="mysql-cluster-mgm-client-commands"/>).
</para>
</listitem>
@@ -10331,16 +10335,17 @@
<para>
<literal><replaceable>node_id</replaceable> START</literal>
</para>
-
+
<para>
Brings online the data node identified by
<replaceable>node_id</replaceable> (or all data nodes).
</para>
-
+
<para>
- <emphasis role="bold">Important</emphasis>: To use this command to
- bring a data node online, the data node must have been started using
- <command>ndbd --nostart</command> or <command>ndbd -n</command>.
+ <emphasis role="bold">Important</emphasis>: To use this
+ command to bring a data node online, the data node must have
+ been started using <command>ndbd --nostart</command> or
+ <command>ndbd -n</command>.
</para>
</listitem>
@@ -10360,9 +10365,10 @@
<para>
Stops the data node identified by
- <replaceable>node_id</replaceable> (or all data nodes). A data node
- affected by this command disconnects from the cluster, and its
- associated <command>ndbd</command> process terminates.
+ <replaceable>node_id</replaceable> (or all data nodes). A
+ data node affected by this command disconnects from the
+ cluster, and its associated <command>ndbd</command> process
+ terminates.
</para>
</listitem>
@@ -10385,23 +10391,26 @@
Restarts the data node identified by
<replaceable>node_id</replaceable> (or all data nodes).
</para>
-
+
<para>
- Using the <option>-i</option> option with <literal>RESTART</literal>
- causes the data node to perform an initial restart; that is, the
- node's filesystem is deleted and recreated. The effect is the same
- as that obtained from stopping the data node process and then starting
- it again using <command>ndbd --initial</command> from the system shell.
+ Using the <option>-i</option> option with
+ <literal>RESTART</literal> causes the data node to perform
+ an initial restart; that is, the node's filesystem is
+ deleted and recreated. The effect is the same as that
+ obtained from stopping the data node process and then
+ starting it again using <command>ndbd --initial</command>
+ from the system shell.
</para>
-
+
<para>
- Using the <option>-n</option> option causes the data node process to
- be restarted, but the data node is not actually brought online until
- the appropriate <literal>START</literal> command is issued. The
- effect of this option is the same as that obtained from stopping the
+ Using the <option>-n</option> option causes the data node
+ process to be restarted, but the data node is not actually
+ brought online until the appropriate
+ <literal>START</literal> command is issued. The effect of
+ this option is the same as that obtained from stopping the
data node and then starting it again using <literal>ndbd
- --nostart</literal> or <literal>ndbd -n</literal> from the system
- shell.
+ --nostart</literal> or <literal>ndbd -n</literal> from the
+ system shell.
</para>
</listitem>
@@ -10476,64 +10485,66 @@
database.
</para>
</listitem>
-
+
<listitem>
<indexterm>
<primary>MySQL Cluster</primary>
<secondary><literal>EXIT</literal> command</secondary>
</indexterm>
-
+
<indexterm>
<primary><literal>EXIT</literal> command (MySQL Cluster)</primary>
</indexterm>
-
+
<indexterm>
<primary>MySQL Cluster</primary>
<secondary><literal>QUIT</literal> command</secondary>
</indexterm>
-
+
<indexterm>
<primary><literal>QUIT</literal> command (MySQL Cluster)</primary>
</indexterm>
-
+
<para>
<literal>QUIT</literal>, <literal>EXIT</literal>
</para>
-
+
<para>
Terminates the management client.
</para>
-
+
<para>
- This command does not affect any nodes connected to the cluster.
+ This command does not affect any nodes connected to the
+ cluster.
</para>
</listitem>
-
+
<listitem>
<indexterm>
<primary>MySQL Cluster</primary>
<secondary><literal>SHUTDOWN</literal> command</secondary>
</indexterm>
-
+
<indexterm>
<primary><literal>SHUTDOWN</literal> command (MySQL Cluster)</primary>
</indexterm>
-
+
<para>
<literal>SHUTDOWN</literal>
</para>
-
+
<para>
- Shuts down all cluster data nodes and management nodes. To exit the
- management client after this has been done, use
+ Shuts down all cluster data nodes and management nodes. To
+ exit the management client after this has been done, use
<literal>EXIT</literal> or <literal>QUIT</literal>.
</para>
-
+
<para>
- This command does <emphasis>not</emphasis> shut down any SQL nodes
- or API nodes that are connected to the cluster.
+ This command does <emphasis>not</emphasis> shut down any SQL
+ nodes or API nodes that are connected to the cluster.
</para>
</listitem>
+
</itemizedlist>
</section>
Modified: trunk/refman-5.0/mysql-cluster.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster.xml 2006-08-22 02:38:35 UTC (rev 3077)
+++ trunk/refman-5.0/mysql-cluster.xml 2006-08-22 02:40:51 UTC (rev 3078)
Changed blocks: 10, Lines Added: 75, Lines Deleted: 66; 10591 bytes
@@ -7971,10 +7971,10 @@
<xref
linkend="mysql-cluster-configuration"/>.
</para>
-
+
<para>
- This section remains in development, and continues to be updated and
- expanded.
+ This section remains in development, and continues to be updated
+ and expanded.
</para>
<section id="mysql-cluster-rolling-restart">
@@ -8418,18 +8418,19 @@
</tr>
</tbody>
</table>
-
+
<para>
In the previous table, <emphasis role="bold">Stop</emphasis> and
- <emphasis role="bold">Start</emphasis> steps indicate that the process
- must be stopped completely using a shell command (such as
- <command>kill</command> on most Unix systems) or the management client
- <literal>STOP</literal> command, then started again from a system shell
- by invoking the <command>ndbd</command> or <command>ndb_mgmd</command>
- executable as appropriate. <emphasis role="bold">Restart</emphasis>
- indicates the process may be restarted using the
- <command>ndb_mgm</command> management client <literal>RESTART</literal>
- command.
+ <emphasis role="bold">Start</emphasis> steps indicate that the
+ process must be stopped completely using a shell command (such
+ as <command>kill</command> on most Unix systems) or the
+ management client <literal>STOP</literal> command, then started
+ again from a system shell by invoking the
+ <command>ndbd</command> or <command>ndb_mgmd</command>
+ executable as appropriate.
+ <emphasis role="bold">Restart</emphasis> indicates the process
+ may be restarted using the <command>ndb_mgm</command> management
+ client <literal>RESTART</literal> command.
</para>
</section>
@@ -9328,13 +9329,14 @@
section. Users of earlier MySQL Cluster versions should note
that some of these options have been changed from those in MySQL
4.1 Cluster to make them consistent with one another as well as
- with <command>mysqld</command>. You can use the <option>--help</option>
- option with any MySQL Cluster executable to view a list of the options
- which it supports.
+ with <command>mysqld</command>. You can use the
+ <option>--help</option> option with any MySQL Cluster executable
+ to view a list of the options which it supports.
</para>
-
+
<para>
- The following options are common to all MySQL Cluster executables:
+ The following options are common to all MySQL Cluster
+ executables:
</para>
<itemizedlist>
@@ -9424,20 +9426,21 @@
<para>
<option>--version</option>, <option>-V</option>
</para>
-
+
<para>
- Prints the MySQL Cluster version number of the executable. The
- version number is relevant because not all versions can be used
- together, and the MySQL Cluster startup process verifies that the
- versions of the binaries being used can co-exist in the same
- cluster. This is also important when performing an online (rolling)
- software upgrade or downgrade of MySQL Cluster. (See
+ Prints the MySQL Cluster version number of the executable.
+ The version number is relevant because not all versions can
+ be used together, and the MySQL Cluster startup process
+ verifies that the versions of the binaries being used can
+ co-exist in the same cluster. This is also important when
+ performing an online (rolling) software upgrade or downgrade
+ of MySQL Cluster. (See
<xref linkend="mysql-cluster-rolling-restart"/>).
</para>
</listitem>
</itemizedlist>
-
+
<para>
The next few sections describe options specific to individual
<literal>NDB</literal> programs.
@@ -9704,7 +9707,7 @@
<para>
<option>--nostart</option>, <option>-n</option>
</para>
-
+
<para>
Instructs <command>ndbd</command> not to start
automatically. When this option is used,
@@ -9714,7 +9717,7 @@
the execution engine until specifically requested to do so
by the management server. This can be accomplished by
issuing the proper <literal>START</literal> command in the
- management client (see
+ management client (see
<xref linkend="mysql-cluster-mgm-client-commands"/>).
</para>
</listitem>
@@ -10368,11 +10371,12 @@
<emphasis role="bold">Note</emphasis>: <literal>ALL
START</literal> continues to affect data nodes only.
</para>
-
+
<para>
- <emphasis role="bold">Important</emphasis>: To use this command to
- bring a data node online, the data node must have been started using
- <command>ndbd --nostart</command> or <command>ndbd -n</command>.
+ <emphasis role="bold">Important</emphasis>: To use this
+ command to bring a data node online, the data node must have
+ been started using <command>ndbd --nostart</command> or
+ <command>ndbd -n</command>.
</para>
</listitem>
@@ -10401,11 +10405,11 @@
<emphasis role="bold">Note</emphasis>: <literal>ALL
STOP</literal> continues to affect data nodes only.
</para>
-
+
<para>
- A node affected by this command disconnects from the cluster, and
- its associated <command>ndbd</command> or
- <command>ndb_mgmd</command> process terminates.
+ A node affected by this command disconnects from the
+ cluster, and its associated <command>ndbd</command> or
+ <command>ndb_mgmd</command> process terminates.
</para>
</listitem>
@@ -10428,23 +10432,26 @@
Restarts the data node identified by
<replaceable>node_id</replaceable> (or all data nodes).
</para>
-
+
<para>
- Using the <option>-i</option> option with <literal>RESTART</literal>
- causes the data node to perform an initial restart; that is, the
- node's filesystem is deleted and recreated. The effect is the same
- as that obtained from stopping the data node process and then starting
- it again using <command>ndbd --initial</command> from the system shell.
+ Using the <option>-i</option> option with
+ <literal>RESTART</literal> causes the data node to perform
+ an initial restart; that is, the node's filesystem is
+ deleted and recreated. The effect is the same as that
+ obtained from stopping the data node process and then
+ starting it again using <command>ndbd --initial</command>
+ from the system shell.
</para>
-
+
<para>
- Using the <option>-n</option> option causes the data node process to
- be restarted, but the data node is not actually brought online until
- the appropriate <literal>START</literal> command is issued. The
- effect of this option is the same as that obtained from stopping the
+ Using the <option>-n</option> option causes the data node
+ process to be restarted, but the data node is not actually
+ brought online until the appropriate
+ <literal>START</literal> command is issued. The effect of
+ this option is the same as that obtained from stopping the
data node and then starting it again using <literal>ndbd
- --nostart</literal> or <literal>ndbd -n</literal> from the system
- shell.
+ --nostart</literal> or <literal>ndbd -n</literal> from the
+ system shell.
</para>
</listitem>
@@ -10519,64 +10526,66 @@
database.
</para>
</listitem>
-
+
<listitem>
<indexterm>
<primary>MySQL Cluster</primary>
<secondary><literal>EXIT</literal> command</secondary>
</indexterm>
-
+
<indexterm>
<primary><literal>EXIT</literal> command (MySQL Cluster)</primary>
</indexterm>
-
+
<indexterm>
<primary>MySQL Cluster</primary>
<secondary><literal>QUIT</literal> command</secondary>
</indexterm>
-
+
<indexterm>
<primary><literal>QUIT</literal> command (MySQL Cluster)</primary>
</indexterm>
-
+
<para>
<literal>QUIT</literal>, <literal>EXIT</literal>
</para>
-
+
<para>
Terminates the management client.
</para>
-
+
<para>
- This command does not affect any nodes connected to the cluster.
+ This command does not affect any nodes connected to the
+ cluster.
</para>
</listitem>
-
+
<listitem>
<indexterm>
<primary>MySQL Cluster</primary>
<secondary><literal>SHUTDOWN</literal> command</secondary>
</indexterm>
-
+
<indexterm>
<primary><literal>SHUTDOWN</literal> command (MySQL Cluster)</primary>
</indexterm>
-
+
<para>
<literal>SHUTDOWN</literal>
</para>
-
+
<para>
- Shuts down all cluster data nodes and management nodes. To exit the
- management client after this has been done, use
+ Shuts down all cluster data nodes and management nodes. To
+ exit the management client after this has been done, use
<literal>EXIT</literal> or <literal>QUIT</literal>.
</para>
-
+
<para>
- This command does <emphasis>not</emphasis> shut down any SQL nodes
- or API nodes that are connected to the cluster.
+ This command does <emphasis>not</emphasis> shut down any SQL
+ nodes or API nodes that are connected to the cluster.
</para>
</listitem>
+
</itemizedlist>
</section>
Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml 2006-08-22 02:38:35 UTC (rev 3077)
+++ trunk/refman-5.1/mysql-cluster.xml 2006-08-22 02:40:51 UTC (rev 3078)
Changed blocks: 13, Lines Added: 81, Lines Deleted: 71; 11553 bytes
@@ -7852,8 +7852,8 @@
</para>
<para>
- This section remains in development, and continues to be updated and
- expanded.
+ This section remains in development, and continues to be updated
+ and expanded.
</para>
<section id="mysql-cluster-rolling-restart">
@@ -8297,18 +8297,19 @@
</tr>
</tbody>
</table>
-
+
<para>
In the previous table, <emphasis role="bold">Stop</emphasis> and
- <emphasis role="bold">Start</emphasis> steps indicate that the process
- must be stopped completely using a shell command (such as
- <command>kill</command> on most Unix systems) or the management client
- <literal>STOP</literal> command, then started again from a system shell
- by invoking the <command>ndbd</command> or <command>ndb_mgmd</command>
- executable as appropriate. <emphasis role="bold">Restart</emphasis>
- indicates the process may be restarted using the
- <command>ndb_mgm</command> management client <literal>RESTART</literal>
- command.
+ <emphasis role="bold">Start</emphasis> steps indicate that the
+ process must be stopped completely using a shell command (such
+ as <command>kill</command> on most Unix systems) or the
+ management client <literal>STOP</literal> command, then started
+ again from a system shell by invoking the
+ <command>ndbd</command> or <command>ndb_mgmd</command>
+ executable as appropriate.
+ <emphasis role="bold">Restart</emphasis> indicates the process
+ may be restarted using the <command>ndb_mgm</command> management
+ client <literal>RESTART</literal> command.
</para>
</section>
@@ -9205,14 +9206,16 @@
All MySQL Cluster executables (except for
<command>mysqld</command>) take the options described in this
section. Users of earlier MySQL Cluster versions should note
- that some of these options have been changed to make them consistent
- with one another as well as with <command>mysqld</command>. You can use
- the <option>--help</option> option with any MySQL Cluster executable to
- view a list of the options which it supports.
+ that some of these options have been changed to make them
+ consistent with one another as well as with
+ <command>mysqld</command>. You can use the
+ <option>--help</option> option with any MySQL Cluster executable
+ to view a list of the options which it supports.
</para>
-
+
<para>
- The following options are common to all MySQL Cluster executables:
+ The following options are common to all MySQL Cluster
+ executables:
</para>
<itemizedlist>
@@ -9304,18 +9307,19 @@
</para>
<para>
- Prints the MySQL Cluster version number of the executable. The
- version number is relevant because not all versions can be used
- together, and the MySQL Cluster startup process verifies that the
- versions of the binaries being used can co-exist in the same
- cluster. This is also important when performing an online (rolling)
- software upgrade or downgrade of MySQL Cluster. (See
+ Prints the MySQL Cluster version number of the executable.
+ The version number is relevant because not all versions can
+ be used together, and the MySQL Cluster startup process
+ verifies that the versions of the binaries being used can
+ co-exist in the same cluster. This is also important when
+ performing an online (rolling) software upgrade or downgrade
+ of MySQL Cluster. (See
<xref linkend="mysql-cluster-rolling-restart"/>).
</para>
</listitem>
</itemizedlist>
-
+
<para>
The next few sections describe options specific to individual
<literal>NDB</literal> programs.
@@ -9480,24 +9484,26 @@
</itemizedlist>
<para>
- This option does <emphasis>not</emphasis> affect either of the
- following:
+ This option does <emphasis>not</emphasis> affect either of
+ the following:
</para>
-
+
<itemizedlist>
+
<listitem>
<para>
Backup files that have already been created by the
affected node
</para>
</listitem>
-
+
<listitem>
<para>
- Cluster Disk Data files (see
+ Cluster Disk Data files (see
<xref linkend="mysql-cluster-disk-data"/>).
</para>
</listitem>
+
</itemizedlist>
<para>
@@ -9598,7 +9604,7 @@
<para>
<option>--nostart</option>, <option>-n</option>
</para>
-
+
<para>
Instructs <command>ndbd</command> not to start
automatically. When this option is used,
@@ -9608,7 +9614,7 @@
the execution engine until specifically requested to do so
by the management server. This can be accomplished by
issuing the proper <literal>START</literal> command in the
- management client (see
+ management client (see
<xref linkend="mysql-cluster-mgm-client-commands"/>).
</para>
</listitem>
@@ -10255,21 +10261,22 @@
<para>
<literal><replaceable>node_id</replaceable> START</literal>
</para>
-
+
<para>
Brings online the data node identified by
<replaceable>node_id</replaceable> (or all data nodes).
</para>
-
- <para>
- <literal>ALL START</literal> works on all data nodes only, and does
- not affect management nodes.
+
+ <para>
+ <literal>ALL START</literal> works on all data nodes only,
+ and does not affect management nodes.
</para>
-
+
<para>
- <emphasis role="bold">Important</emphasis>: To use this command to
- bring a data node online, the data node must have been started using
- <command>ndbd --nostart</command> or <command>ndbd -n</command>.
+ <emphasis role="bold">Important</emphasis>: To use this
+ command to bring a data node online, the data node must have
+ been started using <command>ndbd --nostart</command> or
+ <command>ndbd -n</command>.
</para>
</listitem>
@@ -10293,11 +10300,11 @@
STOP</literal> works to start all data nodes only, and does
not affect management nodes.
</para>
-
+
<para>
- A node affected by this command disconnects from the cluster, and
- its associated <command>ndbd</command> or
- <command>ndb_mgmd</command> process terminates.
+ A node affected by this command disconnects from the
+ cluster, and its associated <command>ndbd</command> or
+ <command>ndb_mgmd</command> process terminates.
</para>
</listitem>
@@ -10320,25 +10327,27 @@
Restarts the data node identified by
<replaceable>node_id</replaceable> (or all data nodes).
</para>
-
+
<para>
- Using the <option>-i</option> option with <literal>RESTART</literal>
- causes the data node to perform an initial restart; that is, the
- node's filesystem is deleted and recreated. The effect is the same
- as that obtained from stopping the data node process and then starting
- it again using <command>ndbd --initial</command> from the system
- shell. Note that backup files and Disk Data files are not removed
- when this option is used.
+ Using the <option>-i</option> option with
+ <literal>RESTART</literal> causes the data node to perform
+ an initial restart; that is, the node's filesystem is
+ deleted and recreated. The effect is the same as that
+ obtained from stopping the data node process and then
+ starting it again using <command>ndbd --initial</command>
+ from the system shell. Note that backup files and Disk Data
+ files are not removed when this option is used.
</para>
-
+
<para>
- Using the <option>-n</option> option causes the data node process to
- be restarted, but the data node is not actually brought online until
- the appropriate <literal>START</literal> command is issued. The
- effect of this option is the same as that obtained from stopping the
+ Using the <option>-n</option> option causes the data node
+ process to be restarted, but the data node is not actually
+ brought online until the appropriate
+ <literal>START</literal> command is issued. The effect of
+ this option is the same as that obtained from stopping the
data node and then starting it again using <literal>ndbd
- --nostart</literal> or <literal>ndbd -n</literal> from the system
- shell.
+ --nostart</literal> or <literal>ndbd -n</literal> from the
+ system shell.
</para>
</listitem>
@@ -10419,16 +10428,16 @@
<primary>MySQL Cluster</primary>
<secondary><literal>EXIT</literal> command</secondary>
</indexterm>
-
+
<indexterm>
<primary><literal>EXIT</literal> command (MySQL Cluster)</primary>
</indexterm>
-
+
<indexterm>
<primary>MySQL Cluster</primary>
<secondary><literal>QUIT</literal> command</secondary>
</indexterm>
-
+
<indexterm>
<primary><literal>QUIT</literal> command (MySQL Cluster)</primary>
</indexterm>
@@ -10440,9 +10449,10 @@
<para>
Terminates the management client.
</para>
-
+
<para>
- This command does not affect any nodes connected to the cluster.
+ This command does not affect any nodes connected to the
+ cluster.
</para>
</listitem>
@@ -10459,16 +10469,16 @@
<para>
<literal>SHUTDOWN</literal>
</para>
-
+
<para>
- Shuts down all cluster data nodes and management nodes. To exit the
- management client after this has been done, use
+ Shuts down all cluster data nodes and management nodes. To
+ exit the management client after this has been done, use
<literal>EXIT</literal> or <literal>QUIT</literal>.
</para>
-
+
<para>
- This command does <emphasis>not</emphasis> shut down any SQL nodes
- or API nodes that are connected to the cluster.
+ This command does <emphasis>not</emphasis> shut down any SQL
+ nodes or API nodes that are connected to the cluster.
</para>
</listitem>
Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml 2006-08-22 02:38:35 UTC (rev 3077)
+++ trunk/refman-5.1/partitioning.xml 2006-08-22 02:40:51 UTC (rev 3078)
Changed blocks: 3, Lines Added: 30, Lines Deleted: 28; 3946 bytes
@@ -4379,12 +4379,12 @@
this restriction does not apply, and you may use any column or
columns in the partitioning expression.
</para>
-
- <para>
- This also means that you cannot later add a primary or unique key to a
- partitioned table unless the primary key or unique key includes all
- columns used for the partitioning key. Consider given the
- partitioned table defined as shown here:
+
+ <para>
+ This also means that you cannot later add a primary or unique
+ key to a partitioned table unless the primary key or unique
+ key includes all columns used for the partitioning key.
+ Consider given the partitioned table defined as shown here:
</para>
<programlisting>
@@ -4421,14 +4421,14 @@
# fails with ERROR 1482
ALTER TABLE t_no_pk ADD PRIMARY KEY(c2);
</programlisting>
-
+
<para>
- These rules also apply to existing non-partitioned tables that you
- wish to partition using <literal>ALTER TABLE ... PARTITION
- BY</literal>. Consider a table <literal>np_pk</literal> defined as
- shown here:
+ These rules also apply to existing non-partitioned tables that
+ you wish to partition using <literal>ALTER TABLE ... PARTITION
+ BY</literal>. Consider a table <literal>np_pk</literal>
+ defined as shown here:
</para>
-
+
<programlisting>
CREATE TABLE np_pk (
id INT NOT NULL AUTO_INCREMENT PRIMARY KEY,
@@ -4436,44 +4436,46 @@
added DATE
);
</programlisting>
-
+
<para>
- The following <literal>ALTER TABLE</literal> statements fails with an
- error, because the <literal>added</literal> column is not part of the
- table's primary key:
+ The following <literal>ALTER TABLE</literal> statements fails
+ with an error, because the <literal>added</literal> column is
+ not part of the table's primary key:
</para>
-
+
<programlisting>
ALTER TABLE np_pk
PARTITION BY HASH( TO_DAYS(added) )
PARTITIONS 4;
</programlisting>
-
+
<para>
This statement, however, is valid:
</para>
-
+
<programlisting>
ALTER TABLE np_pk
PARTITION BY HASH(id)
PARTITIONS 4;
</programlisting>
-
+
<para>
- In the case of <literal>np_pk</literal>, the only column that may be
- used as part of a partitioning expression is <literal>id</literal>; if
- you wish to partition this table using any other columns for the
- partitioning key, you must first modify the table's primary key,
- either by adding the desired columns to the primary key, or by
- dropping the primary key altogether.
+ In the case of <literal>np_pk</literal>, the only column that
+ may be used as part of a partitioning expression is
+ <literal>id</literal>; if you wish to partition this table
+ using any other columns for the partitioning key, you must
+ first modify the table's primary key, either by adding the
+ desired columns to the primary key, or by dropping the primary
+ key altogether.
</para>
</listitem>
<listitem>
<para>
Subpartitions are limited to <literal>HASH</literal> or
- <literal>KEY</literal> partitioning. <literal>HASH</literal> and
- <literal>KEY</literal> partitions cannot be subpartitioned.
+ <literal>KEY</literal> partitioning. <literal>HASH</literal>
+ and <literal>KEY</literal> partitions cannot be
+ subpartitioned.
</para>
</listitem>
Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml 2006-08-22 02:38:35 UTC (rev 3077)
+++ trunk/refman-5.1/sql-syntax.xml 2006-08-22 02:40:51 UTC (rev 3078)
Changed blocks: 3, Lines Added: 25, Lines Deleted: 24; 4176 bytes
@@ -848,7 +848,7 @@
repartitioning, for adding, dropping, merging, and splitting
partitions, and for performing partitioning maintenance.
</para>
-
+
<para>
Simply using a <replaceable>partition_options</replaceable>
clause with <literal>ALTER TABLE</literal> on a partitioned
@@ -860,44 +860,45 @@
<replaceable>partition_options</replaceable> clause for
<literal>CREATE TABLE</literal> (see
<xref linkend="create-table"/>, for more detailed
- information), and can also be used to partition an existing table
- that is not already partitioned. For example, consider a
- (non-partitioned) table defined as shown here:
+ information), and can also be used to partition an existing
+ table that is not already partitioned. For example, consider
+ a (non-partitioned) table defined as shown here:
</para>
-
+
<programlisting>
CREATE TABLE t1 (
id INT,
year_col INT
);
</programlisting>
-
+
<para>
- This table can be partitioned by <literal>RANGE</literal> using the
- <literal>id</literal> column as the partitioning key into 8
- partitions by means of this statement:
+ This table can be partitioned by <literal>RANGE</literal>
+ using the <literal>id</literal> column as the partitioning
+ key into 8 partitions by means of this statement:
</para>
-
+
<programlisting>
ALTER TABLE t1
PARTITION BY HASH(id)
PARTITIONS 8;
</programlisting>
-
+
<para>
- The table that results from using an <literal>ALTER TABLE ...
- PARTITION BY</literal> statement must follow the same rules as one
- created using <literal>CREATE TABLE ... PARTITION BY</literal>. This
- includes the rules governing the relationship between a table's
- primary key (or possibly unique key) and the column or columns used
- in its partitioning expression, as discussed in
+ The table that results from using an <literal>ALTER TABLE
+ ... PARTITION BY</literal> statement must follow the same
+ rules as one created using <literal>CREATE TABLE ...
+ PARTITION BY</literal>. This includes the rules governing
+ the relationship between a table's primary key (or possibly
+ unique key) and the column or columns used in its
+ partitioning expression, as discussed in
<link linkend="partitioning-limitations-partitioning-keys-primary-keys">Partitioning
- Limitations & Partitioning Keys and Primary Keys</link>.
+ Limitations & Partitioning Keys and Primary Keys</link>.
</para>
-
+
<para>
- <literal>ALTER TABLE ... PARTITION BY</literal> was first implemented in
- MySQL 5.1.6.
+ <literal>ALTER TABLE ... PARTITION BY</literal> was first
+ implemented in MySQL 5.1.6.
</para>
<para>
@@ -15744,15 +15745,15 @@
<para>
<literal>RESTORE TABLE</literal> restores the table or tables
from a backup that was made with <literal>BACKUP
- TABLE</literal>. The directory should be specified as a full
+ TABLE</literal>. The directory should be specified as a full
pathname.
</para>
-
+
<para>
Existing tables are not overwritten; if you try to restore
over an existing table, an error occurs. Just as for
<literal>BACKUP TABLE</literal>, <literal>RESTORE
- TABLE</literal> currently works only for
+ TABLE</literal> currently works only for
<literal>MyISAM</literal> tables. Restored tables are not
replicated from master to slave.
</para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r3078 - in trunk: refman-4.1 refman-5.0 refman-5.1 | jon | 22 Aug |
