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

[paul]

Author: paul
Date: 2007-05-08 19:36:10 +0200 (Tue, 08 May 2007)
New Revision: 6373

Log:
 r24668@polar:  paul | 2007-05-08 12:05:40 -0500
 Add note about spurious MERGE table corruption. (Bug#25647)


Modified:
   trunk/refman-4.1/storage-engines.xml
   trunk/refman-5.0/se-merge.xml
   trunk/refman-5.1/se-merge.xml

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


Modified: trunk/refman-4.1/storage-engines.xml
===================================================================
--- trunk/refman-4.1/storage-engines.xml	2007-05-08 01:53:14 UTC (rev 6372)
+++ trunk/refman-4.1/storage-engines.xml	2007-05-08 17:36:10 UTC (rev 6373)
Changed blocks: 1, Lines Added: 25, Lines Deleted: 13; 2755 bytes

@@ -2144,20 +2144,32 @@
 
         <listitem>
           <para>
-            You cannot use <literal>DROP TABLE</literal>,
<literal>ALTER
-            TABLE</literal>, <literal>DELETE</literal> without a
-            <literal>WHERE</literal> clause, <literal>REPAIR
-            TABLE</literal>, <literal>TRUNCATE TABLE</literal>,
-            <literal>OPTIMIZE TABLE</literal>, or <literal>ANALYZE
-            TABLE</literal> on any of the tables that are mapped into an
-            open <literal>MERGE</literal> table. If you do so, the
-            <literal>MERGE</literal> table may still refer to the
-            original table, which yields unexpected results. The easiest
-            way to work around this deficiency is to ensure that no
-            <literal>MERGE</literal> tables remain open by issuing a
-            <literal>FLUSH TABLES</literal> statement prior to
-            performing any of those operations.
+            You cannot use <literal>REPAIR TABLE</literal>,
+            <literal>OPTIMIZE TABLE</literal>, <literal>DROP
+            TABLE</literal>, <literal>ALTER TABLE</literal>,
+            <literal>DELETE</literal> without a
<literal>WHERE</literal>
+            clause, <literal>TRUNCATE TABLE</literal>, or
+            <literal>ANALYZE TABLE</literal> on any of the tables that
+            are mapped into an open <literal>MERGE</literal> table. If
+            you do so, the <literal>MERGE</literal> table may still
+            refer to the original table, which yields unexpected
+            results. The easiest way to work around this deficiency is
+            to ensure that no <literal>MERGE</literal> tables remain
+            open by issuing a <literal>FLUSH TABLES</literal> statement
+            prior to performing any of those operations.
           </para>
+
+          <para>
+            The unexpected results include the possibility that the
+            operation on the <literal>MERGE</literal> table will report
+            table corruption. However, if this occurs after operations
+            on the underlying <literal>MyISAM</literal> tables such as
+            those listed in the previous paragraph (<literal>REPAIR
+            TABLE</literal>, <literal>OPTIMIZE TABLE</literal>, and so
+            forth), the corruption message is spurious. To deal with
+            this, issue a <literal>FLUSH TABLES</literal> statement
+            after modifying the <literal>MyISAM</literal> tables.
+          </para>
         </listitem>
 
         <listitem>


Modified: trunk/refman-5.0/se-merge.xml
===================================================================
--- trunk/refman-5.0/se-merge.xml	2007-05-08 01:53:14 UTC (rev 6372)
+++ trunk/refman-5.0/se-merge.xml	2007-05-08 17:36:10 UTC (rev 6373)
Changed blocks: 2, Lines Added: 17, Lines Deleted: 5; 1962 bytes

@@ -528,11 +528,11 @@
 
       <listitem>
         <para>
-          You cannot use <literal>DROP TABLE</literal>, <literal>ALTER
-          TABLE</literal>, <literal>DELETE</literal> without a
-          <literal>WHERE</literal> clause, <literal>REPAIR
-          TABLE</literal>, <literal>TRUNCATE TABLE</literal>,
-          <literal>OPTIMIZE TABLE</literal>, or <literal>ANALYZE
+          You cannot use <literal>REPAIR TABLE</literal>,
+          <literal>OPTIMIZE TABLE</literal>, <literal>DROP
+          TABLE</literal>, <literal>ALTER TABLE</literal>,
+          <literal>DELETE</literal> without a
<literal>WHERE</literal>
+          clause, <literal>TRUNCATE TABLE</literal>, or
<literal>ANALYZE
           TABLE</literal> on any of the tables that are mapped into an
           open <literal>MERGE</literal> table. If you do so, the
           <literal>MERGE</literal> table may still refer to the original

@@ -542,6 +542,18 @@
           <literal>FLUSH TABLES</literal> statement prior to performing
           any of those operations.
         </para>
+
+        <para>
+          The unexpected results include the possibility that the
+          operation on the <literal>MERGE</literal> table will report
+          table corruption. However, if this occurs after operations on
+          the underlying <literal>MyISAM</literal> tables such as those
+          listed in the previous paragraph (<literal>REPAIR
+          TABLE</literal>, <literal>OPTIMIZE TABLE</literal>, and so
+          forth), the corruption message is spurious. To deal with this,
+          issue a <literal>FLUSH TABLES</literal> statement after
+          modifying the <literal>MyISAM</literal> tables.
+        </para>
       </listitem>
 
       <listitem>


Modified: trunk/refman-5.1/se-merge.xml
===================================================================
--- trunk/refman-5.1/se-merge.xml	2007-05-08 01:53:14 UTC (rev 6372)
+++ trunk/refman-5.1/se-merge.xml	2007-05-08 17:36:10 UTC (rev 6373)
Changed blocks: 2, Lines Added: 17, Lines Deleted: 5; 1962 bytes

@@ -520,11 +520,11 @@
 
       <listitem>
         <para>
-          You cannot use <literal>DROP TABLE</literal>, <literal>ALTER
-          TABLE</literal>, <literal>DELETE</literal> without a
-          <literal>WHERE</literal> clause, <literal>REPAIR
-          TABLE</literal>, <literal>TRUNCATE TABLE</literal>,
-          <literal>OPTIMIZE TABLE</literal>, or <literal>ANALYZE
+          You cannot use <literal>REPAIR TABLE</literal>,
+          <literal>OPTIMIZE TABLE</literal>, <literal>DROP
+          TABLE</literal>, <literal>ALTER TABLE</literal>,
+          <literal>DELETE</literal> without a
<literal>WHERE</literal>
+          clause, <literal>TRUNCATE TABLE</literal>, or
<literal>ANALYZE
           TABLE</literal> on any of the tables that are mapped into an
           open <literal>MERGE</literal> table. If you do so, the
           <literal>MERGE</literal> table may still refer to the original

@@ -534,6 +534,18 @@
           <literal>FLUSH TABLES</literal> statement prior to performing
           any of those operations.
         </para>
+
+        <para>
+          The unexpected results include the possibility that the
+          operation on the <literal>MERGE</literal> table will report
+          table corruption. However, if this occurs after operations on
+          the underlying <literal>MyISAM</literal> tables such as those
+          listed in the previous paragraph (<literal>REPAIR
+          TABLE</literal>, <literal>OPTIMIZE TABLE</literal>, and so
+          forth), the corruption message is spurious. To deal with this,
+          issue a <literal>FLUSH TABLES</literal> statement after
+          modifying the <literal>MyISAM</literal> tables.
+        </para>
       </listitem>
 
       <listitem>