List:Commits« Previous MessageNext Message »
From:stefan Date:January 29 2006 1:55pm
Subject:svn commit - mysqldoc@docsrva: r1101 - trunk/refman-5.1
View as plain text  
Author: shinz
Date: 2006-01-29 14:55:07 +0100 (Sun, 29 Jan 2006)
New Revision: 1101

Log:
--replicate-*-table behaviour depends on whether SBR or RBR are enabled (Lars)

Modified:
   trunk/refman-5.1/replication.xml

Modified: trunk/refman-5.1/replication.xml
===================================================================
--- trunk/refman-5.1/replication.xml	2006-01-29 13:40:12 UTC (rev 1100)
+++ trunk/refman-5.1/replication.xml	2006-01-29 13:55:07 UTC (rev 1101)
@@ -3272,18 +3272,37 @@
 
           <listitem>
             <para>
-              <emphasis>Yes</emphasis>: Proceed to the next step and
-              begin evaluating the table rules in the order shown (first
-              the non-wild rules, and then the wild rules). Only tables
-              that are to be updated are compared to the rules
-              (<literal>INSERT INTO sales SELECT * FROM
-              prices</literal>: only <literal>sales</literal> is
-              compared to the rules). If several tables are to be
-              updated (multiple-table statement), the first matching
-              table (matching <quote>do</quote> or
-              <quote>ignore</quote>) wins. That is, the first table is
-              compared to the rules. Then, if no decision could be made,
-              the second table is compared to the rules, and so on.
+              <emphasis>Yes</emphasis>: In this case, the behaviour
+              depends on whether statement-based replication or
+              row-based replication are enabled:
+              <itemizedlist>
+                <listitem>
+                  <para>
+                    <emphasis>Statement-based replication</emphasis>:
+                    Proceed to the next step and
+                    begin evaluating the table rules in the order shown (first
+                    the non-wild rules, and then the wild rules). Only tables
+                    that are to be updated are compared to the rules
+                    (<literal>INSERT INTO sales SELECT * FROM
+                      prices</literal>: only <literal>sales</literal> is
+                    compared to the rules). If several tables are to be
+                    updated (multiple-table statement), the first matching
+                    table (matching <quote>do</quote> or
+                    <quote>ignore</quote>) wins. That is, the first table is
+                    compared to the rules. Then, if no decision could be made,
+                    the second table is compared to the rules, and so on.
+                  </para>
+                </listitem>
+                <listitem>
+                  <para>
+                    <emphasis>Row-based replication</emphasis>:
+                    All table row changes are filtered individually. For
+                    multi-table updates, each table is filtered separately
+                    according to the rules. Some may be changed and some not,
+                    depending on the rules (and the actual changes, of course).
+                  </para>
+                </listitem>
+              </itemizedlist>
             </para>
           </listitem>
 

Thread
svn commit - mysqldoc@docsrva: r1101 - trunk/refman-5.1stefan29 Jan