From: jon
Date: October 7 2006 6:14am
Subject: svn commit - mysqldoc@docsrva: r3570 - in trunk: refman-5.0 refman-5.1
List-Archive: http://lists.mysql.com/commits/13289
Message-Id: <200610070614.k976EffI026969@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Author: jstephens
Date: 2006-10-07 08:14:38 +0200 (Sat, 07 Oct 2006)
New Revision: 3570

Log:

As of 5.0.26/5.1.12, LOAD DATA INFILE no longer causes an implicit
commit, except for NDBCluster. (This is now in line with the behaviour
of this statement in <= 4.1.)

Bug #11151



Modified:
   trunk/refman-5.0/mysql-cluster.xml
   trunk/refman-5.0/news-5.0.xml
   trunk/refman-5.0/se-innodb.xml
   trunk/refman-5.0/sql-syntax.xml
   trunk/refman-5.1/mysql-cluster.xml
   trunk/refman-5.1/news-5.1.xml
   trunk/refman-5.1/se-innodb.xml
   trunk/refman-5.1/sql-syntax.xml


Modified: trunk/refman-5.0/mysql-cluster.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster.xml	2006-10-07 05:56:26 UTC (rev 3569)
+++ trunk/refman-5.0/mysql-cluster.xml	2006-10-07 06:14:38 UTC (rev 3570)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 2; 811 bytes

@@ -15941,9 +15941,10 @@
                   <listitem>
                     <para>
                       <literal>LOAD DATA INFILE</literal> is not
-                      transactional. During such an operation the
+                      transactional when used on <literal>NDB</literal>
+                      tables. <emphasis>During such an operation, the
                       <literal>NDB</literal> engine can and does commit
-                      at will.
+                      at will.</emphasis>
                     </para>
 
                     <para>


Modified: trunk/refman-5.0/news-5.0.xml
===================================================================
--- trunk/refman-5.0/news-5.0.xml	2006-10-07 05:56:26 UTC (rev 3569)
+++ trunk/refman-5.0/news-5.0.xml	2006-10-07 06:14:38 UTC (rev 3570)
Changed blocks: 6, Lines Added: 29, Lines Deleted: 11; 3257 bytes

@@ -322,6 +322,15 @@
           alternatives. (Bug #18822)
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          <literal>LOAD DATA INFILE</literal> no longer causes an
+          implicit commit for all storage storage engines. It now causes
+          an implicit commit only for tables using the
+          <literal>NDB</literal> storage engine. (Bug #11151)
+        </para>
+      </listitem>
 
       <listitem>
         <para>

@@ -10714,7 +10723,7 @@
       <listitem>
         <para>
           Replication of <literal>LOAD DATA INFILE</literal> failed
-          between systems that use different pathname syntax (such as
+          between systems using different pathname syntax (such as
           delimiter characters). (Bug #11815)
         </para>
       </listitem>

@@ -16065,12 +16074,12 @@
 
       <listitem>
         <para>
-          If on replication master a <literal>LOAD DATA INFILE</literal>
-          is interrupted in the middle (integrity constraint violation,
-          killed connection...), the slave used to skip this
-          <literal>LOAD DATA INFILE</literal> entirely, thus missing
-          some changes if this command permanently inserted/updated some
-          table records before being interrupted. This is now fixed.
+          If, on a replication master a <literal>LOAD DATA
+            INFILE</literal> operation was interrupted (by, for example,
+          an integrity constraint violation or killed connection), the
+          slave skipped the <literal>LOAD DATA INFILE</literal>
+          entirely, thus missing changes if this command permanently
+          inserted or updated table records before being interrupted.
           (Bug #3247)
         </para>
       </listitem>

@@ -18756,7 +18765,7 @@
 
       <listitem>
         <para>
-          Fixed <command>mysqlbinlog</command> not to forget to print a
+          <command>mysqlbinlog</command> failed to print a
           <literal>USE</literal> statement under rare circumstances
           where the binary log contained a <literal>LOAD DATA
           INFILE</literal> statement. (Bug #3415)

@@ -18765,9 +18774,9 @@
 
       <listitem>
         <para>
-          Fixed a memory corruption when replicating a <literal>LOAD
-          DATA INFILE</literal> when the master had version 3.23. (Bug
-          #3422)
+          Fixed memory corruption occurring when replicating a
+          <literal>LOAD DATA INFILE</literal> from a master running
+          MySQL version 3.23. (Bug #3422)
         </para>
       </listitem>
 

@@ -19015,6 +19024,15 @@
           changed compared to that of MySQL 4.1 and older.
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          <literal>LOAD DATA INFILE</literal> causes an implicit commit.
+          <emphasis role="bold">Important</emphasis>: The behaviour of
+          <literal>LOAD DATA INFILE</literal> in this regard was changed
+          again in MySQL 5.0.26. See <xref linkend="news-5-0-26"/>.
+        </para>
+      </listitem>
 
     </itemizedlist>
 


Modified: trunk/refman-5.0/se-innodb.xml
===================================================================
--- trunk/refman-5.0/se-innodb.xml	2006-10-07 05:56:26 UTC (rev 3569)
+++ trunk/refman-5.0/se-innodb.xml	2006-10-07 06:14:38 UTC (rev 3570)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 677 bytes

@@ -4528,6 +4528,14 @@
             statements the user made during that transaction.
           </para>
         </listitem>
+        
+        <listitem>
+          <para>
+            Prior to MySQL 5.0.26, <literal>LOAD DATA INFILE</literal>
+            also caused an implicit commit for <literal>InnoDB</literal>
+            tables (as was true for all storage engines). 
+          </para>
+        </listitem>
 
       </itemizedlist>
 


Modified: trunk/refman-5.0/sql-syntax.xml
===================================================================
--- trunk/refman-5.0/sql-syntax.xml	2006-10-07 05:56:26 UTC (rev 3569)
+++ trunk/refman-5.0/sql-syntax.xml	2006-10-07 06:14:38 UTC (rev 3570)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 0; 818 bytes

@@ -10959,6 +10959,16 @@
             statements the user made during that transaction.
           </para>
         </listitem>
+        
+        <listitem>
+          <para>
+            In MySQL 5.0.25 and earlier, <literal>LOAD DATA
+              INFILE</literal> caused an implicit commit for all storage
+            engines. Beginning with MySQL 5.0.26, it causes an implicit
+            commit only for tables using the <literal>NDB</literal> storage
+            engine. For more information, see Bug #11151.
+          </para>
+        </listitem>
 
       </itemizedlist>
 


Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml	2006-10-07 05:56:26 UTC (rev 3569)
+++ trunk/refman-5.1/mysql-cluster.xml	2006-10-07 06:14:38 UTC (rev 3570)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 2; 811 bytes

@@ -18377,9 +18377,10 @@
                   <listitem>
                     <para>
                       <literal>LOAD DATA INFILE</literal> is not
-                      transactional. During such an operation the
+                      transactional when used on <literal>NDB</literal>
+                      tables. <emphasis>During such an operation, the
                       <literal>NDB</literal> engine can and does commit
-                      at will.
+                      at will.</emphasis>
                     </para>
 
                     <para>


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2006-10-07 05:56:26 UTC (rev 3569)
+++ trunk/refman-5.1/news-5.1.xml	2006-10-07 06:14:38 UTC (rev 3570)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 0; 714 bytes

@@ -678,6 +678,15 @@
           <xref linkend="udf-compiling"/>. (Bug #19121)
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          <literal>LOAD DATA INFILE</literal> no longer causes an
+          implicit commit for all storage storage engines. It now causes
+          an implicit commit only for tables using the
+          <literal>NDB</literal> storage engine. (Bug #11151)
+        </para>
+      </listitem>
 
       <listitem>
         <para>


Modified: trunk/refman-5.1/se-innodb.xml
===================================================================
--- trunk/refman-5.1/se-innodb.xml	2006-10-07 05:56:26 UTC (rev 3569)
+++ trunk/refman-5.1/se-innodb.xml	2006-10-07 06:14:38 UTC (rev 3570)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 677 bytes

@@ -4491,6 +4491,14 @@
             statements the user made during that transaction.
           </para>
         </listitem>
+        
+        <listitem>
+          <para>
+            Prior to MySQL 5.1.12, <literal>LOAD DATA INFILE</literal>
+            also caused an implicit commit for <literal>InnoDB</literal>
+            tables (as was true for all storage engines). 
+          </para>
+        </listitem>
 
       </itemizedlist>
 


Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml	2006-10-07 05:56:26 UTC (rev 3569)
+++ trunk/refman-5.1/sql-syntax.xml	2006-10-07 06:14:38 UTC (rev 3570)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 0; 818 bytes

@@ -12297,6 +12297,16 @@
             statements the user made during that transaction.
           </para>
         </listitem>
+        
+        <listitem>
+          <para>
+            In MySQL 5.1.11 and earlier, <literal>LOAD DATA
+              INFILE</literal> caused an implicit commit for all storage
+            engines. Beginning with MySQL 5.1.12, it causes an implicit
+            commit only for tables using the <literal>NDB</literal> storage
+            engine. For more information, see Bug #11151.
+          </para>
+        </listitem>
 
       </itemizedlist>