From: Date: April 10 2008 5:56pm
Subject: svn commit - mysqldoc@docsrva: r10443 - in trunk: it/refman-5.1 pt/refman-5.1 refman-4.1 refman-5.0 refman-5.1 refman-6.0
List-Archive: http://lists.mysql.com/commits/45206
Message-Id: <200804101556.m3AFuiMk002776@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Author: jstephens
Date: 2008-04-10 17:56:43 +0200 (Thu, 10 Apr 2008)
New Revision: 10443

Log:

CONCURRENT replicated by RBR, but not replicated by SBR

(Ref. Bug #34628 - Thanks, Sveta!)



Modified:
   trunk/it/refman-5.1/replication-notes.xml
   trunk/it/refman-5.1/sql-syntax.xml
   trunk/pt/refman-5.1/replication-notes.xml
   trunk/pt/refman-5.1/sql-syntax.xml
   trunk/refman-4.1/replication.xml
   trunk/refman-4.1/sql-syntax.xml
   trunk/refman-5.0/replication-notes.xml
   trunk/refman-5.0/sql-syntax.xml
   trunk/refman-5.1/replication-notes.xml
   trunk/refman-5.1/sql-syntax.xml
   trunk/refman-6.0/replication-notes.xml
   trunk/refman-6.0/sql-syntax.xml


Modified: trunk/it/refman-5.1/replication-notes.xml
===================================================================
--- trunk/it/refman-5.1/replication-notes.xml	2008-04-10 14:23:13 UTC (rev 10442)
+++ trunk/it/refman-5.1/replication-notes.xml	2008-04-10 15:56:43 UTC (rev 10443)
Changed blocks: 1, Lines Added: 12, Lines Deleted: 0; 1024 bytes

@@ -958,6 +958,18 @@
         running MySQL 4.0 or earlier.
       </para>
 
+      <para>
+        When using statement-based replication, the <literal>LOAD DATA
+        INFILE</literal> statement&apos;s <literal>CONCURRENT</literal>
+        option is not replicated; that is, <literal>LOAD DATA CONCURRENT
+        INFILE</literal> is replicated as <literal>LOAD DATA
+        INFILE</literal>, and <literal>LOAD DATA CONCURRENT LOCAL
+        INFILE</literal> is replicated as <literal>LOAD DATA LOCAL
+        INFILE</literal>. The <literal>CONCURRENT</literal> option
+        <emphasis>is</emphasis> replicated when using row-based
+        replication. (Bug #34628)
+      </para>
+
     </section>
 
     <section id="replication-features-mastercrash">


Modified: trunk/it/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/it/refman-5.1/sql-syntax.xml	2008-04-10 14:23:13 UTC (rev 10442)
+++ trunk/it/refman-5.1/sql-syntax.xml	2008-04-10 15:56:43 UTC (rev 10443)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 757 bytes

@@ -7927,6 +7927,14 @@
         even if no other thread is using the table at the same time.
       </para>
 
+      <para>
+        <literal>CONCURRENT</literal> is not replicated when using
+        statement-based replication; however, it is replicated when
+        using row-based replication. See
+        <xref linkend="replication-features-load-data"/>, for more
+        information.
+      </para>
+
       <note>
         <para>
           Prior to MySQL 5.1.23, <literal>LOAD DATA</literal> performed


Modified: trunk/pt/refman-5.1/replication-notes.xml
===================================================================
--- trunk/pt/refman-5.1/replication-notes.xml	2008-04-10 14:23:13 UTC (rev 10442)
+++ trunk/pt/refman-5.1/replication-notes.xml	2008-04-10 15:56:43 UTC (rev 10443)
Changed blocks: 1, Lines Added: 12, Lines Deleted: 0; 1024 bytes

@@ -958,6 +958,18 @@
         running MySQL 4.0 or earlier.
       </para>
 
+      <para>
+        When using statement-based replication, the <literal>LOAD DATA
+        INFILE</literal> statement&apos;s <literal>CONCURRENT</literal>
+        option is not replicated; that is, <literal>LOAD DATA CONCURRENT
+        INFILE</literal> is replicated as <literal>LOAD DATA
+        INFILE</literal>, and <literal>LOAD DATA CONCURRENT LOCAL
+        INFILE</literal> is replicated as <literal>LOAD DATA LOCAL
+        INFILE</literal>. The <literal>CONCURRENT</literal> option
+        <emphasis>is</emphasis> replicated when using row-based
+        replication. (Bug #34628)
+      </para>
+
     </section>
 
     <section id="replication-features-mastercrash">


Modified: trunk/pt/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/pt/refman-5.1/sql-syntax.xml	2008-04-10 14:23:13 UTC (rev 10442)
+++ trunk/pt/refman-5.1/sql-syntax.xml	2008-04-10 15:56:43 UTC (rev 10443)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 757 bytes

@@ -7927,6 +7927,14 @@
         even if no other thread is using the table at the same time.
       </para>
 
+      <para>
+        <literal>CONCURRENT</literal> is not replicated when using
+        statement-based replication; however, it is replicated when
+        using row-based replication. See
+        <xref linkend="replication-features-load-data"/>, for more
+        information.
+      </para>
+
       <note>
         <para>
           Prior to MySQL 5.1.23, <literal>LOAD DATA</literal> performed


Modified: trunk/refman-4.1/replication.xml
===================================================================
--- trunk/refman-4.1/replication.xml	2008-04-10 14:23:13 UTC (rev 10442)
+++ trunk/refman-4.1/replication.xml	2008-04-10 15:56:43 UTC (rev 10443)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 0; 877 bytes

@@ -1807,6 +1807,16 @@
           such cases, it is best to upgrade the master to 5.0 or later.
           (Bug #31240)
         </para>
+
+        <para>
+          The <literal>LOAD DATA INFILE</literal> statement&apos;s
+          <literal>CONCURRENT</literal> option is not replicated; that
+          is, <literal>LOAD DATA CONCURRENT INFILE</literal> is
+          replicated as <literal>LOAD DATA INFILE</literal>, and
+          <literal>LOAD DATA CONCURRENT LOCAL INFILE</literal> is
+          replicated as <literal>LOAD DATA LOCAL INFILE</literal>. (Bug
+          #34628)
+        </para>
       </listitem>
 
       <listitem>


Modified: trunk/refman-4.1/sql-syntax.xml
===================================================================
--- trunk/refman-4.1/sql-syntax.xml	2008-04-10 14:23:13 UTC (rev 10442)
+++ trunk/refman-4.1/sql-syntax.xml	2008-04-10 15:56:43 UTC (rev 10443)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 0; 606 bytes

@@ -5518,6 +5518,11 @@
       </para>
 
       <para>
+        <literal>CONCURRENT</literal> is not replicated. See
+        <xref linkend="replication-features"/>, for more information.
+      </para>
+
+      <para>
         The <literal>LOCAL</literal> keyword, if specified, is
         interpreted with respect to the client end of the connection:
       </para>


Modified: trunk/refman-5.0/replication-notes.xml
===================================================================
--- trunk/refman-5.0/replication-notes.xml	2008-04-10 14:23:13 UTC (rev 10442)
+++ trunk/refman-5.0/replication-notes.xml	2008-04-10 15:56:43 UTC (rev 10443)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 0; 965 bytes

@@ -519,6 +519,15 @@
       </para>
 
       <para>
+        The <literal>LOAD DATA INFILE</literal> statement&apos;s
+        <literal>CONCURRENT</literal> option is not replicated; that is,
+        <literal>LOAD DATA CONCURRENT INFILE</literal> is replicated as
+        <literal>LOAD DATA INFILE</literal>, and <literal>LOAD DATA
+        CONCURRENT LOCAL INFILE</literal> is replicated as <literal>LOAD
+        DATA LOCAL INFILE</literal>. (Bug #34628)
+      </para>
+
+      <para>
         <emphasis>The following applies only if either the master or the
         slave is running MySQL version 5.0.3 or older</emphasis>: If on
         the master a <literal>LOAD DATA INFILE</literal> is interrupted


Modified: trunk/refman-5.0/sql-syntax.xml
===================================================================
--- trunk/refman-5.0/sql-syntax.xml	2008-04-10 14:23:13 UTC (rev 10442)
+++ trunk/refman-5.0/sql-syntax.xml	2008-04-10 15:56:43 UTC (rev 10443)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 0; 619 bytes

@@ -5563,6 +5563,12 @@
       </para>
 
       <para>
+        <literal>CONCURRENT</literal> is not replicated. See
+        <xref linkend="replication-features-load"/>, for more
+        information.
+      </para>
+
+      <para>
         The <literal>LOCAL</literal> keyword, if specified, is
         interpreted with respect to the client end of the connection:
       </para>


Modified: trunk/refman-5.1/replication-notes.xml
===================================================================
--- trunk/refman-5.1/replication-notes.xml	2008-04-10 14:23:13 UTC (rev 10442)
+++ trunk/refman-5.1/replication-notes.xml	2008-04-10 15:56:43 UTC (rev 10443)
Changed blocks: 1, Lines Added: 12, Lines Deleted: 0; 1015 bytes

@@ -999,6 +999,18 @@
         running MySQL 4.0 or earlier.
       </para>
 
+      <para>
+        When using statement-based replication, the <literal>LOAD DATA
+        INFILE</literal> statement&apos;s <literal>CONCURRENT</literal>
+        option is not replicated; that is, <literal>LOAD DATA CONCURRENT
+        INFILE</literal> is replicated as <literal>LOAD DATA
+        INFILE</literal>, and <literal>LOAD DATA CONCURRENT LOCAL
+        INFILE</literal> is replicated as <literal>LOAD DATA LOCAL
+        INFILE</literal>. The <literal>CONCURRENT</literal> option
+        <emphasis>is</emphasis> replicated when using row-based
+        replication. (Bug #34628)
+      </para>
+
     </section>
 
     <section id="replication-features-mastercrash">


Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml	2008-04-10 14:23:13 UTC (rev 10442)
+++ trunk/refman-5.1/sql-syntax.xml	2008-04-10 15:56:43 UTC (rev 10443)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 748 bytes

@@ -7944,6 +7944,14 @@
         even if no other thread is using the table at the same time.
       </para>
 
+      <para>
+        <literal>CONCURRENT</literal> is not replicated when using
+        statement-based replication; however, it is replicated when
+        using row-based replication. See
+        <xref linkend="replication-features-load-data"/>, for more
+        information.
+      </para>
+
       <note>
         <para>
           Prior to MySQL 5.1.23, <literal>LOAD DATA</literal> performed


Modified: trunk/refman-6.0/replication-notes.xml
===================================================================
--- trunk/refman-6.0/replication-notes.xml	2008-04-10 14:23:13 UTC (rev 10442)
+++ trunk/refman-6.0/replication-notes.xml	2008-04-10 15:56:43 UTC (rev 10443)
Changed blocks: 1, Lines Added: 12, Lines Deleted: 0; 1015 bytes

@@ -968,6 +968,18 @@
         running MySQL 4.0 or earlier.
       </para>
 
+      <para>
+        When using statement-based replication, the <literal>LOAD DATA
+        INFILE</literal> statement&apos;s <literal>CONCURRENT</literal>
+        option is not replicated; that is, <literal>LOAD DATA CONCURRENT
+        INFILE</literal> is replicated as <literal>LOAD DATA
+        INFILE</literal>, and <literal>LOAD DATA CONCURRENT LOCAL
+        INFILE</literal> is replicated as <literal>LOAD DATA LOCAL
+        INFILE</literal>. The <literal>CONCURRENT</literal> option
+        <emphasis>is</emphasis> replicated when using row-based
+        replication. (Bug #34628)
+      </para>
+
     </section>
 
     <section id="replication-features-mastercrash">


Modified: trunk/refman-6.0/sql-syntax.xml
===================================================================
--- trunk/refman-6.0/sql-syntax.xml	2008-04-10 14:23:13 UTC (rev 10442)
+++ trunk/refman-6.0/sql-syntax.xml	2008-04-10 15:56:43 UTC (rev 10443)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 747 bytes

@@ -7811,6 +7811,14 @@
         even if no other thread is using the table at the same time.
       </para>
 
+      <para>
+        <literal>CONCURRENT</literal> is not replicated when using
+        statement-based replication; however, it is replicated when
+        using row-based replication. See
+        <xref linkend="replication-features-load-data"/>, for more
+        information.
+      </para>
+
       <note>
         <para>
           Prior to MySQL 6.0.4, <literal>LOAD DATA</literal> performed