[Rt-commit] rt branch, 4.0/reword-upgrading-mysql, created. rt-4.0.2rc1-7-gd7acec3

[Alex Vandiver]

The branch, 4.0/reword-upgrading-mysql has been created
        at  d7acec380d2950b88dc492e07b4de1c2a7bc6432 (commit)

- Log -----------------------------------------------------------------
commit d7acec380d2950b88dc492e07b4de1c2a7bc6432
Author: Alex Vandiver <alexmv at bestpractical.com>
Date:   Tue Aug 9 15:25:28 2011 -0400

    Reorder UPGRADING.mysql to clarify that it is only part of the process
    
    Put the "why" paragraph later, as it is not as important as the logic of
    when these steps are necessary, and making clear that it is not a
    substitute for the full upgrade instructions in README.

diff --git a/docs/UPGRADING.mysql b/docs/UPGRADING.mysql
index 1064075..a2d341c 100644
--- a/docs/UPGRADING.mysql
+++ b/docs/UPGRADING.mysql
@@ -1,18 +1,21 @@
-MySQL 4.1 and greater implemented changes in character set handling that
-may result in RT failures; specifically, multiple login requests, binary
-attachments breakage, image custom fields breakage and more.  In order
-to resolve this issue, we've changed our schema for MySQL 4.1 and above.
-
-If you're installing a new RT installation, you can skip this file
-entirely.
-
-If you're migrating from MySQL 4.0 to MySQL 4.1 or above, then you MUST
-follow instructions at the bottom of this file.
-
-If you're upgrading RT from versions prior to 3.8.0 then you MUST follow
-instructions below even if your old RT was installed on MySQL 4.1 or
-newer.
-
+If you did not start by reading the README file, please start there;
+these steps do not list the full upgrading process, merely a part which
+is sometimes necessary.
+
+This file applies if:
+ 1) You are migrating from MySQL 4.0 to MySQL 4.1 or above
+                      OR
+ 2) You are upgrading RT from versions prior to 3.8.0, even if your old
+    RT was installed on MySQL 4.1 or newer
+
+If neither of the above cases apply, your should upgrade as per the
+instructions in the README.
+
+These changes are necessary because MySQL 4.1 and greater changed some
+aspects of character set handling that may result in RT failures; this
+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.
 
 
 === Upgrading RT from versions prior to 3.8.0 ===

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