summaryrefslogtreecommitdiff
path: root/rt/UPGRADING.mysql
diff options
context:
space:
mode:
authorivan <ivan>2011-02-17 00:25:23 +0000
committerivan <ivan>2011-02-17 00:25:23 +0000
commitfc6209f398899f0211cfcedeb81a3cd65e04a941 (patch)
treebc1dc8876218529948413d85c17cd67508bdd38d /rt/UPGRADING.mysql
parente70abd21bab68b23488f7ef1ee2e693a3b365691 (diff)
import rt 3.8.9
Diffstat (limited to 'rt/UPGRADING.mysql')
-rw-r--r--rt/UPGRADING.mysql5
1 files changed, 3 insertions, 2 deletions
diff --git a/rt/UPGRADING.mysql b/rt/UPGRADING.mysql
index accaa979a..37b0dda42 100644
--- a/rt/UPGRADING.mysql
+++ b/rt/UPGRADING.mysql
@@ -15,7 +15,8 @@ instructions below even if your old RT was installed on MySQL 4.1 or newer.
=== Upgrading RT from versions prior to 3.8.0 ===
-1) Backup RT's database. Test that you can restore from this backup.
+1) Backup RT's database. Use --default-character-set=binary if mysql
+server is 4.1 or newer. Test that you can restore from this backup.
2) Follow instructions in the README file to step 7.
@@ -79,7 +80,7 @@ do the following:
4) Configure MySQL 4.1 and newer to use Latin1 as default character set
everywhere.
5) Import the dump into the new MySQL server, replacing your empty database you
- created at step 1.
+ created at step 1, use --default-character-set=binary on restore.
6) At this point you have RT 3.8.x code base using an old database. You can
upgrade RT using the instructions above.