MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:jon.stephens Date:September 20 2010 5:50pm
Subject:svn commit - mysqldoc@docsrva: r22783 - trunk/refman-5.1
View as plain text  
Author: jstephens
Date: 2010-09-20 19:50:19 +0200 (Mon, 20 Sep 2010)
New Revision: 22783

Log:

BUG#54115 edits



Modified:
   trunk/refman-5.1/mysql-cluster-replication-core.xml


Modified: trunk/refman-5.1/mysql-cluster-replication-core.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-replication-core.xml	2010-09-20 17:17:16 UTC (rev 22782)
+++ trunk/refman-5.1/mysql-cluster-replication-core.xml	2010-09-20 17:50:19 UTC (rev 22783)
Changed blocks: 4, Lines Added: 18, Lines Deleted: 24; 3469 bytes

@@ -3308,23 +3308,16 @@
     </itemizedlist>
 
     <para>
-      If only some but not all columns are sent, then the master and
-      slave can diverge.
+      We refer to the column used for determining updates as a
+      <quote>timestamp</quote> column, but the data type of this column
+      is never <literal role="type">TIMESTAMP</literal>; rather, its
+      data type should be <literal role="type">INT</literal>
+      (<literal role="type">INTEGER</literal>) or
+      <literal role="type">BIGINT</literal>. This
+      <quote>timestamp</quote> column should also be
+      <literal>UNSIGNED</literal> and <literal>NOT NULL</literal>.
     </para>
 
-    <note>
-      <para>
-        We refer to the column used for determining updates as a
-        <quote>timestamp</quote> column, but the data type of this
-        column is never <literal role="type">TIMESTAMP</literal>;
-        rather, its data type should be
-        <literal role="type">INT</literal>
-        (<literal role="type">INTEGER</literal>) or
-        <literal role="type">BIGINT</literal>. This column should be
-        <literal>UNSIGNED</literal> and <literal>NOT NULL</literal>.
-      </para>
-    </note>
-
     <indexterm>
       <primary>--ndb-log-update-as-write (mysqld option)</primary>
     </indexterm>

@@ -3400,10 +3393,10 @@
     </itemizedlist>
 
     <para>
-      It is more efficient to log updated columns only; however, if you
-      need to log full rows, you can do so by setting
-      <option>--ndb-log-updated-only</option> to <literal>0</literal> or
-      <literal>OFF</literal>.
+      It is usually sufficient&mdash;and more efficient&mdash;to log
+      updated columns only; however, if you need to log full rows, you
+      can do so by setting <option>--ndb-log-updated-only</option> to
+      <literal>0</literal> or <literal>OFF</literal>.
     </para>
 
     <para>

@@ -3424,8 +3417,9 @@
       are updates and not writes; that is, such that updates are treated
       as changes in existing rows rather than the writing of new rows
       (even though these replace existing rows). This option is turned
-      on by default; to turn it off, start the server with
-      <option>--ndb-log-update-as-write=0</option> or
+      on by default; in other words, updates are treated as writes. To
+      turn off the option, start the master <command>mysqld</command>
+      with <option>--ndb-log-update-as-write=0</option> or
       <option>--ndb-log-update-as-write=OFF</option>.
     </para>
 

@@ -3743,9 +3737,9 @@
                 <literal>NDB$MAX_DELETE_WIN()</literal>, if the
                 <quote>timestamp</quote> column value for a given row
                 adding or updating an existing row coming from the
-                master is higher than that on the slave, it is applied;
-                however, delete operations are treated as always having
-                the higher value. This is illustrated by the following
+                master is higher than that on the slave, it is applied.
+                However, delete operations are treated as always having
+                the higher value. This is illustrated in the following
                 pseudocode:
               </para>
 


Thread
svn commit - mysqldoc@docsrva: r22783 - trunk/refman-5.1jon.stephens20 Sep