svn commit - mysqldoc@docsrva: r12935 - in trunk: refman-5.1 refman-6.0

[jon]

Author: jstephens
Date: 2008-12-12 10:44:34 +0100 (Fri, 12 Dec 2008)
New Revision: 12935

Log:

USE_FRM option not supported for REPAIR TABLE on partitioned tables

(Thanks, MattiasJ!)



Modified:
   trunk/refman-5.1/sql-syntax-server-administration.xml
   trunk/refman-6.0/sql-syntax-server-administration.xml


Modified: trunk/refman-5.1/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-server-administration.xml	2008-12-12 03:27:14 UTC (rev 12934)
+++ trunk/refman-5.1/sql-syntax-server-administration.xml	2008-12-12 09:44:34 UTC (rev 12935)
Changed blocks: 1, Lines Added: 17, Lines Deleted: 11; 2245 bytes

@@ -2653,23 +2653,29 @@
 
       <para>
         Beginning with MySQL 5.1.27, <literal role="stmt">REPAIR
-        TABLE</literal> is also supported for partitioned tables. Also
-        beginning with MySQL 5.1.27, you can use <literal>ALTER TABLE
-        ... REPAIR PARTITION</literal> to repair one or more partitions;
-        for more information, see <xref linkend="alter-table"/>, and
+        TABLE</literal> is also supported for partitioned tables.
+        However, the <literal>USE_FRM</literal> option cannot be used
+        with this statement on a partitioned table.
+      </para>
+
+      <para>
+        Also beginning with MySQL 5.1.27, you can use <literal>ALTER
+        TABLE ... REPAIR PARTITION</literal> to repair one or more
+        partitions; for more information, see
+        <xref linkend="alter-table"/>, and
         <xref linkend="partitioning-maintenance"/>.
       </para>
 
       <remark role="help-description-end"/>
 
       <para>
-        Normally, you should never have to run this statement. However,
-        if disaster strikes, <literal role="stmt">REPAIR TABLE</literal>
-        is very likely to get back all your data from a
-        <literal>MyISAM</literal> table. If your tables become corrupted
-        often, you should try to find the reason for it, to eliminate
-        the need to use <literal role="stmt">REPAIR TABLE</literal>. See
-        <xref linkend="crashing"/>, and
+        Normally, you should never have to run
+        <literal role="stmt">REPAIR TABLE</literal>. However, if
+        disaster strikes, this statement is very likely to get back all
+        your data from a <literal>MyISAM</literal> table. If your tables
+        become corrupted often, you should try to find the reason for
+        it, to eliminate the need to use <literal role="stmt">REPAIR
+        TABLE</literal>. See <xref linkend="crashing"/>, and
         <xref linkend="myisam-table-problems"/>.
       </para>
 


Modified: trunk/refman-6.0/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-6.0/sql-syntax-server-administration.xml	2008-12-12 03:27:14 UTC (rev 12934)
+++ trunk/refman-6.0/sql-syntax-server-administration.xml	2008-12-12 09:44:34 UTC (rev 12935)
Changed blocks: 1, Lines Added: 17, Lines Deleted: 11; 2242 bytes

@@ -2544,23 +2544,29 @@
 
       <para>
         Beginning with MySQL 6.0.6, <literal role="stmt">REPAIR
-        TABLE</literal> is also supported for partitioned tables. Also
-        beginning with MySQL 6.0.6, you can use <literal>ALTER TABLE ...
-        REPAIR PARTITION</literal> to repair one or more partitions; for
-        more information, see <xref linkend="alter-table"/>, and
+        TABLE</literal> is also supported for partitioned tables.
+        However, the <literal>USE_FRM</literal> option cannot be used
+        with this statement on a partitioned table.
+      </para>
+
+      <para>
+        Also beginning with MySQL 6.0.6, you can use <literal>ALTER
+        TABLE ... REPAIR PARTITION</literal> to repair one or more
+        partitions; for more information, see
+        <xref linkend="alter-table"/>, and
         <xref linkend="partitioning-maintenance"/>.
       </para>
 
       <remark role="help-description-end"/>
 
       <para>
-        Normally, you should never have to run this statement. However,
-        if disaster strikes, <literal role="stmt">REPAIR TABLE</literal>
-        is very likely to get back all your data from a
-        <literal>MyISAM</literal> table. If your tables become corrupted
-        often, you should try to find the reason for it, to eliminate
-        the need to use <literal role="stmt">REPAIR TABLE</literal>. See
-        <xref linkend="crashing"/>, and
+        Normally, you should never have to run
+        <literal role="stmt">REPAIR TABLE</literal>. However, if
+        disaster strikes, this statement is very likely to get back all
+        your data from a <literal>MyISAM</literal> table. If your tables
+        become corrupted often, you should try to find the reason for
+        it, to eliminate the need to use <literal role="stmt">REPAIR
+        TABLE</literal>. See <xref linkend="crashing"/>, and
         <xref linkend="myisam-table-problems"/>.
       </para>