From: jon
Date: April 5 2006 1:28pm
Subject: svn commit - mysqldoc@docsrva: r1729 - in trunk: refman-4.1 refman-5.0 refman-5.1
List-Archive: http://lists.mysql.com/commits/4504
Message-Id: <200604051328.k35DSxhO011473@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Author: jstephens
Date: 2006-04-05 15:28:59 +0200 (Wed, 05 Apr 2006)
New Revision: 1729

Log:

Fixed missing word.



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-04-05 13:08:05 UTC (rev 1728)
+++ trunk/refman-4.1/ndbcluster.xml	2006-04-05 13:28:59 UTC (rev 1729)
@@ -9549,12 +9549,12 @@
               It is not possible to make online schema changes such as
               those accomplished using <literal>ALTER TABLE</literal> or
               <literal>CREATE INDEX</literal>, as the <literal>NDB
-              Cluster</literal> does not support autodiscovery of such
-              changes. (However, you can import or create a table that
-              uses a different storage engine, and then convert it to
-              <literal>NDB</literal> using <literal>ALTER TABLE
-              <replaceable>tbl_name</replaceable>
-              ENGINE=NDBCLUSTER</literal>. In such a case, you must
+                Cluster</literal> engine does not support autodiscovery
+              of such changes. (However, you can import or create a
+              table that uses a different storage engine, and then
+              convert it to <literal>NDB</literal> using <literal>ALTER
+                TABLE <replaceable>tbl_name</replaceable>
+                ENGINE=NDBCLUSTER</literal>. In such a case, you must
               issue a <literal>FLUSH TABLES</literal> statement to force
               the cluster to pick up the change.)
             </para>

Modified: trunk/refman-5.0/ndbcluster.xml
===================================================================
--- trunk/refman-5.0/ndbcluster.xml	2006-04-05 13:08:05 UTC (rev 1728)
+++ trunk/refman-5.0/ndbcluster.xml	2006-04-05 13:28:59 UTC (rev 1729)
@@ -9061,11 +9061,6 @@
 
     <title>&title-mysql-cluster-limitations;</title>
 
-    <remark role="todo">
-      Check this section for relevance to 5.0 and update accordingly
-      (Jeb is assisting with this). [js]
-    </remark>
-
     <remark role="note">
       Changed section title to remove version-specificity. [js]
     </remark>
@@ -9537,14 +9532,14 @@
           <listitem>
             <para>
               It is not possible to make online schema changes such as
-              those accomplished using <literal>ALTER TABLE</literal> or
+              those accomplished using <literal>ALTER TABLE</literal> or              
               <literal>CREATE INDEX</literal>, as the <literal>NDB
-              Cluster</literal> does not support autodiscovery of such
-              changes. (However, you can import or create a table that
-              uses a different storage engine, and then convert it to
-              <literal>NDB</literal> using <literal>ALTER TABLE
-              <replaceable>tbl_name</replaceable>
-              ENGINE=NDBCLUSTER</literal>. In such a case, you must
+                Cluster</literal> engine does not support autodiscovery
+              of such changes. (However, you can import or create a
+              table that uses a different storage engine, and then
+              convert it to <literal>NDB</literal> using <literal>ALTER
+                TABLE <replaceable>tbl_name</replaceable>
+                ENGINE=NDBCLUSTER</literal>. In such a case, you must
               issue a <literal>FLUSH TABLES</literal> statement to force
               the cluster to pick up the change.)
             </para>

Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml	2006-04-05 13:08:05 UTC (rev 1728)
+++ trunk/refman-5.1/ndbcluster.xml	2006-04-05 13:28:59 UTC (rev 1729)
@@ -11576,14 +11576,14 @@
           <listitem>
             <para>
               It is not possible to make online schema changes such as
-              those accomplished using <literal>ALTER TABLE</literal> or
+              those accomplished using <literal>ALTER TABLE</literal> or              
               <literal>CREATE INDEX</literal>, as the <literal>NDB
-              Cluster</literal> does not support autodiscovery of such
-              changes. (However, you can import or create a table that
-              uses a different storage engine, and then convert it to
-              <literal>NDB</literal> using <literal>ALTER TABLE
-              <replaceable>tbl_name</replaceable>
-              ENGINE=NDBCLUSTER</literal>. In such a case, you must
+                Cluster</literal> engine does not support autodiscovery
+              of such changes. (However, you can import or create a
+              table that uses a different storage engine, and then
+              convert it to <literal>NDB</literal> using <literal>ALTER
+                TABLE <replaceable>tbl_name</replaceable>
+                ENGINE=NDBCLUSTER</literal>. In such a case, you must
               issue a <literal>FLUSH TABLES</literal> statement to force
               the cluster to pick up the change.)
             </para>