svn commit - mysqldoc@docsrva: r3007 - in trunk: refman-4.1 refman-5.0 refman-5.1

[jon]

Author: jstephens
Date: 2006-08-13 15:20:30 +0200 (Sun, 13 Aug 2006)
New Revision: 3007

Log:
A single INSERT or REPLACE that sends multiple rows is still one statement
and uses a single request/packet. (Suggested by M. Ham)

Modified:
   trunk/refman-4.1/problems.xml
   trunk/refman-5.0/problems.xml
   trunk/refman-5.1/problems.xml


Modified: trunk/refman-4.1/problems.xml
===================================================================
--- trunk/refman-4.1/problems.xml	2006-08-11 18:29:07 UTC (rev 3006)
+++ trunk/refman-4.1/problems.xml	2006-08-13 13:20:30 UTC (rev 3007)
Changed blocks: 2, Lines Added: 11, Lines Deleted: 1; 1317 bytes

@@ -1073,7 +1073,7 @@
             The problem on Windows is that in some cases MySQL doesn't
             get an error from the OS when writing to the TCP/IP
             connection to the server, but instead gets the error when
-            trying to read the answer from connection.
+            trying to read the answer from the connection.
           </para>
 
           <para>

@@ -1111,6 +1111,16 @@
             setting the packet size is given in
             <xref linkend="packet-too-large"/>.
           </para>
+          
+          <para>
+            An <literal>INSERT</literal> or
<literal>REPLACE</literal>
+            statement that inserts a great many rows can also cause
+            these sorts of errors. Either one of these statements sends
+            a single request to the server irrespective of the number of
+            rows to be inserted; thus, you can often avoid the error by
+            reducing the number of rows sent per
+            <literal>INSERT</literal> or
<literal>REPLACE</literal>.   
+          </para>
         </listitem>
 
         <listitem>


Modified: trunk/refman-5.0/problems.xml
===================================================================
--- trunk/refman-5.0/problems.xml	2006-08-11 18:29:07 UTC (rev 3006)
+++ trunk/refman-5.0/problems.xml	2006-08-13 13:20:30 UTC (rev 3007)
Changed blocks: 2, Lines Added: 11, Lines Deleted: 1; 1317 bytes

@@ -1073,7 +1073,7 @@
             The problem on Windows is that in some cases MySQL doesn't
             get an error from the OS when writing to the TCP/IP
             connection to the server, but instead gets the error when
-            trying to read the answer from connection.
+            trying to read the answer from the connection.
           </para>
 
           <para>

@@ -1112,6 +1112,16 @@
             setting the packet size is given in
             <xref linkend="packet-too-large"/>.
           </para>
+          
+          <para>
+            An <literal>INSERT</literal> or
<literal>REPLACE</literal>
+            statement that inserts a great many rows can also cause
+            these sorts of errors. Either one of these statements sends
+            a single request to the server irrespective of the number of
+            rows to be inserted; thus, you can often avoid the error by
+            reducing the number of rows sent per
+            <literal>INSERT</literal> or
<literal>REPLACE</literal>.   
+          </para>
         </listitem>
 
         <listitem>


Modified: trunk/refman-5.1/problems.xml
===================================================================
--- trunk/refman-5.1/problems.xml	2006-08-11 18:29:07 UTC (rev 3006)
+++ trunk/refman-5.1/problems.xml	2006-08-13 13:20:30 UTC (rev 3007)
Changed blocks: 2, Lines Added: 11, Lines Deleted: 1; 1317 bytes

@@ -1073,7 +1073,7 @@
             The problem on Windows is that in some cases MySQL doesn't
             get an error from the OS when writing to the TCP/IP
             connection to the server, but instead gets the error when
-            trying to read the answer from connection.
+            trying to read the answer from the connection.
           </para>
 
           <para>

@@ -1112,6 +1112,16 @@
             setting the packet size is given in
             <xref linkend="packet-too-large"/>.
           </para>
+          
+          <para>
+            An <literal>INSERT</literal> or
<literal>REPLACE</literal>
+            statement that inserts a great many rows can also cause
+            these sorts of errors. Either one of these statements sends
+            a single request to the server irrespective of the number of
+            rows to be inserted; thus, you can often avoid the error by
+            reducing the number of rows sent per
+            <literal>INSERT</literal> or
<literal>REPLACE</literal>.   
+          </para>
         </listitem>
 
         <listitem>