[Rt-commit] rt branch, 4.0/reword-upgrading-mysql, updated. rt-4.0.2rc1-12-g744935a

[Ruslan Zakirov]

The branch, 4.0/reword-upgrading-mysql has been updated
       via  744935a9f5f2a1f975770c55e2bece91359fd616 (commit)
      from  f4091200dbf5ba982e65e23c8c5ebed744e76b18 (commit)

Summary of changes:
 docs/UPGRADING.mysql |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

- Log -----------------------------------------------------------------
commit 744935a9f5f2a1f975770c55e2bece91359fd616
Author: Ruslan Zakirov <ruz at bestpractical.com>
Date:   Fri Aug 12 17:44:04 2011 +0400

    cover situation when people move DB when upgrade
    
    also, mysql 4.0 has no --default-character-set=binary
    option, it's 4.1+ feature

diff --git a/docs/UPGRADING.mysql b/docs/UPGRADING.mysql
index a553845..f65cabc 100644
--- a/docs/UPGRADING.mysql
+++ b/docs/UPGRADING.mysql
@@ -18,9 +18,9 @@ will manifest as multiple login requests, corrupted binary attachments,
 and corrupted image custom fields, among others.  In order to resolve
 this issue, the upgrade process will need to modify the schema.
 
- 1) If you are migrating from MySQL 4.0 to MySQL 4.1 or above:
-   1a) Dump the database from your MySQL 4.0; be sure to pass the
-       mysqldump command the --default-character-set=binary option.
+ 1) If you are moving database and/or upgrading MySQL
+   1a) Dump the database; with MySQL 4.1 and greater be sure to pass
+       the mysqldump command the --default-character-set=binary option.
        This is necessary because the data was originally encoded in
        Latin1.
 

-----------------------------------------------------------------------