svn commit - mysqldoc@docsrva: r5306 - in trunk: . refman-5.0 refman-5.1

[paul]

Author: paul
Date: 2007-03-12 16:44:07 +0100 (Mon, 12 Mar 2007)
New Revision: 5306

Log:
 r17539@frost:  paul | 2007-03-12 10:04:38 -0500
 Fix typo.


Modified:
   trunk/refman-5.0/optimization.xml
   trunk/refman-5.1/optimization.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:21154
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:17536
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:14593
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:21154
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:17539
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:14593


Modified: trunk/refman-5.0/optimization.xml
===================================================================
--- trunk/refman-5.0/optimization.xml	2007-03-12 15:05:23 UTC (rev 5305)
+++ trunk/refman-5.0/optimization.xml	2007-03-12 15:44:07 UTC (rev 5306)
Changed blocks: 3, Lines Added: 4, Lines Deleted: 4; 1948 bytes

@@ -6202,13 +6202,13 @@
             table has no free blocks in the middle of the data file, you
             can <literal>INSERT</literal> new rows into it at the same
             time that other threads are reading from the table.
-            <xref linkend="concurrent-inserts"/>. If it is important to
+            If it is important to
             be able to do this, you should consider using the table in
             ways that avoid deleting rows. Another possibility is to run
             <literal>OPTIMIZE TABLE</literal> to defragment the table
             after you have deleted a lot of rows from it. This behavior
             is altered by setting the
-            <literal>concurrent_inserts</literal> variable. You can
+            <literal>concurrent_insert</literal> variable. You can
             force new rows to be appended (and therefore allow
             concurrent inserts), even in tables that have deleted rows.
             See <xref linkend="concurrent-inserts"/>.

@@ -6749,7 +6749,7 @@
 
       <para>
         This behavior is altered by the
-        <literal>concurrent_inserts</literal> system variable. See
+        <literal>concurrent_insert</literal> system variable. See
         <xref linkend="concurrent-inserts"/>.
       </para>
 

@@ -7213,7 +7213,7 @@
 
       <para>
         The above is the default behavior, which can be controlled
-        through the <literal>concurrent_inserts</literal> system
+        through the <literal>concurrent_insert</literal> system
         variable. If set to <literal>1</literal> then concurrent inserts
         can occur on MyISAM tables with deleted rows. If set to
         <literal>2</literal> then concurrent inserts are enforced, with


Modified: trunk/refman-5.1/optimization.xml
===================================================================
--- trunk/refman-5.1/optimization.xml	2007-03-12 15:05:23 UTC (rev 5305)
+++ trunk/refman-5.1/optimization.xml	2007-03-12 15:44:07 UTC (rev 5306)
Changed blocks: 3, Lines Added: 4, Lines Deleted: 4; 1948 bytes

@@ -6232,13 +6232,13 @@
             table has no free blocks in the middle of the data file, you
             can <literal>INSERT</literal> new rows into it at the same
             time that other threads are reading from the table.
-            <xref linkend="concurrent-inserts"/>. If it is important to
+            If it is important to
             be able to do this, you should consider using the table in
             ways that avoid deleting rows. Another possibility is to run
             <literal>OPTIMIZE TABLE</literal> to defragment the table
             after you have deleted a lot of rows from it. This behavior
             is altered by setting the
-            <literal>concurrent_inserts</literal> variable. You can
+            <literal>concurrent_insert</literal> variable. You can
             force new rows to be appended (and therefore allow
             concurrent inserts), even in tables that have deleted rows.
             See <xref linkend="concurrent-inserts"/>.

@@ -6769,7 +6769,7 @@
 
       <para>
         This behavior is altered by the
-        <literal>concurrent_inserts</literal> system variable. See
+        <literal>concurrent_insert</literal> system variable. See
         <xref linkend="concurrent-inserts"/>.
       </para>
 

@@ -7228,7 +7228,7 @@
 
       <para>
         The above is the default behavior, which can be controlled
-        through the <literal>concurrent_inserts</literal> system
+        through the <literal>concurrent_insert</literal> system
         variable. If set to <literal>1</literal> then concurrent inserts
         can occur on MyISAM tables with deleted rows. If set to
         <literal>2</literal> then concurrent inserts are enforced, with