List:Commits« Previous MessageNext Message »
From:jon Date:January 9 2006 5:56am
Subject:svn commit - mysqldoc@docsrva: r734 - in trunk: refman-4.1 refman-5.0 refman-5.1
View as plain text  
Author: jstephens
Date: 2006-01-09 06:56:13 +0100 (Mon, 09 Jan 2006)
New Revision: 734

Log:

Fix wording (thanks, Paul!)

Also use SCHEMA rather than DATABASE keyword in RefMan-5.1.



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-01-09 05:10:00 UTC (rev 733)
+++ trunk/refman-4.1/ndbcluster.xml	2006-01-09 05:56:13 UTC (rev 734)
@@ -9064,11 +9064,11 @@
 
           <listitem>
             <para>
-              MySQL replication will not work correctly off if updates
-              are done on multiple MySQL servers. However, if the
-              database partitioning scheme done at the application
-              level, and no transactions take place across these
-              partitions, then replication can be made to work.
+              MySQL replication will not work correctly if updates are
+              done on multiple MySQL servers. However, if the database
+              partitioning scheme is done at the application level, and
+              no transactions take place across these partitions, then
+              replication can be made to work.
             </para>
           </listitem>
 

Modified: trunk/refman-5.0/ndbcluster.xml
===================================================================
--- trunk/refman-5.0/ndbcluster.xml	2006-01-09 05:10:00 UTC (rev 733)
+++ trunk/refman-5.0/ndbcluster.xml	2006-01-09 05:56:13 UTC (rev 734)
@@ -9044,8 +9044,8 @@
             <para>
               MySQL replication will not work correctly if updates are
               done on multiple MySQL servers. However, if the database
-              partitioning scheme done at the application level, and no
-              transactions take place across these partitions, then
+              partitioning scheme is done at the application level, and
+              no transactions take place across these partitions, then
               replication can be made to work.
             </para>
           </listitem>

Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml	2006-01-09 05:10:00 UTC (rev 733)
+++ trunk/refman-5.1/ndbcluster.xml	2006-01-09 05:56:13 UTC (rev 734)
@@ -10655,7 +10655,7 @@
             <para>
               MySQL replication will not work correctly if updates are
               done on multiple MySQL servers. However, if the database
-              partitioning scheme done at the application level, and no
+              partitioning scheme is done at the application level, and no
               transactions take place across these partitions, then
               replication can be made to work.
             </para>
@@ -10669,13 +10669,11 @@
               this means is that after a database named
               <replaceable>db_name</replaceable> is created or imported
               using one MySQL server, you should issue a <literal>CREATE
-              DATABASE <replaceable>db_name</replaceable>;</literal>
+              SCHEMA <replaceable>db_name</replaceable>;</literal>
               statement on each additional MySQL server that access the
-              same MySQL Cluster. (As of MySQL 5.0.2 you may also use
-              <literal>CREATE SCHEMA
-              <replaceable>db_name</replaceable>;</literal>.) Once this
-              has been done for a given MySQL server, that server should
-              be able to detect the database tables without error.
+              same MySQL Cluster. Once this has been done for a given
+              MySQL server, that server should be able to detect the
+              database tables without error.
             </para>
           </listitem>
 

Thread
svn commit - mysqldoc@docsrva: r734 - in trunk: refman-4.1 refman-5.0 refman-5.1jon9 Jan