Author: paul
Date: 2008-05-22 18:09:39 +0200 (Thu, 22 May 2008)
New Revision: 10819
Log:
r31643@frost: paul | 2008-05-22 11:09:37 -0500
Changes related to Bug#36055.
Modified:
trunk/refman-6.0/sql-syntax.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:31640
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:31388
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:31643
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:31388
Modified: trunk/refman-6.0/sql-syntax.xml
===================================================================
--- trunk/refman-6.0/sql-syntax.xml 2008-05-22 16:06:11 UTC (rev 10818)
+++ trunk/refman-6.0/sql-syntax.xml 2008-05-22 16:09:39 UTC (rev 10819)
Changed blocks: 2, Lines Added: 40, Lines Deleted: 6; 3241 bytes
@@ -18691,6 +18691,23 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ As of MySQL 6.0.6, if your table was created by a
+ different version of the MySQL server than the one you are
+ currently running, <literal>FOR UPGRADE</literal>
+ indicates that the table has an <filename>.frm</filename>
+ file with an incompatible version. In this case, the
+ result set returned by <literal>CHECK TABLE</literal>
+ contains a line with a <literal>Msg_type</literal> value
+ of <literal>error</literal> and a
+ <literal>Msg_text</literal> value of <literal>Table
+ upgrade required. Please do "REPAIR TABLE
+ `<replaceable>tbl_name</replaceable>`" to fix
+ it!</literal>
+ </para>
+ </listitem>
+
</itemizedlist>
<para>
@@ -19281,18 +19298,35 @@
performs the upgrade, following the same rules as
<literal>CHECK TABLE ... FOR UPGRADE</literal>. See
<xref linkend="check-table"/>, for more information.
+ <xref linkend="check-table"/>, for more information. As of
+ MySQL 6.0.6, <literal>REPAIR TABLE</literal> without
+ <literal>USE_FRM</literal> upgrades the
+ <filename>.frm</filename> file to the current version.
</para>
<caution>
<para>
- <emphasis>Do not use</emphasis> <literal>USE_FRM</literal>
- if your table was created by a different version of the
- MySQL server than the one you are currently running. Doing
- so risks the loss of all rows in the table. It is
- particularly dangerous to use <literal>USE_FRM</literal>
- after the server returns this message:
+ As of MySQL 6.0.6, if you use <literal>USE_FRM</literal> and
+ your table was created by a different version of the MySQL
+ server than the one you are currently running,
+ <literal>REPAIR TABLE</literal> will not attempt to repair
+ the table. In this case, the result set returned by
+ <literal>REPAIR TABLE</literal> contains a line with a
+ <literal>Msg_type</literal> value of
+ <literal>error</literal> and a <literal>Msg_text</literal>
+ value of <literal>Failed repairing incompatible .FRM
+ file</literal>.
</para>
+ <para>
+ Prior to MySQL 6.0.6, <emphasis>do not use</emphasis>
+ <literal>USE_FRM</literal> if your table was created by a
+ different version of the MySQL server. Doing so risks the
+ loss of all rows in the table. It is particularly dangerous
+ to use <literal>USE_FRM</literal> after the server returns
+ this message:
+ </para>
+
<programlisting>
Table upgrade required. Please do
"REPAIR TABLE `<replaceable>tbl_name</replaceable>`" to fix it!
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10819 - in trunk: . refman-6.0 | paul | 22 May |
