Author: paul
Date: 2006-02-20 14:57:51 +0100 (Mon, 20 Feb 2006)
New Revision: 1401
Log:
r7906@frost: paul | 2006-02-20 07:57:12 -0600
Update upgrade note.
Modified:
trunk/
trunk/refman-5.0/installing.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:7891
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:3223
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:7906
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:3223
Modified: trunk/refman-5.0/installing.xml
===================================================================
--- trunk/refman-5.0/installing.xml 2006-02-20 11:20:11 UTC (rev 1400)
+++ trunk/refman-5.0/installing.xml 2006-02-20 13:57:51 UTC (rev 1401)
@@ -11986,11 +11986,11 @@
<literal>MyISAM</literal> and <literal>InnoDB</literal>
tables created with <literal>DECIMAL</literal> columns in
MySQL 5.0.3 to 5.0.5 will appear corrupt after an upgrade to
- MySQL 5.0.6. Dump such tables with
- <command>mysqldump</command> before upgrading, and then
- reload them after upgrading. (The same incompatibility will
- occur for these tables created in MySQL 5.0.6 after a
- downgrade to MySQL 5.0.3 to 5.0.5.)
+ MySQL 5.0.6. (The same incompatibility will occur for these
+ tables created in MySQL 5.0.6 after a downgrade to MySQL
+ 5.0.3 to 5.0.5.) If you have such tables, check and repair
+ them with <command>mysql_upgrade</command> after upgrading.
+ See <xref linkend="mysql-upgrade"/>.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1401 - in trunk: . refman-5.0 | paul | 20 Feb |
