diff options
author | ivan <ivan> | 2011-02-17 00:25:23 +0000 |
---|---|---|
committer | ivan <ivan> | 2011-02-17 00:25:23 +0000 |
commit | 0fb307c305e4bc2c9c27dc25a3308beae3a4d33c (patch) | |
tree | 9d527e17db4b4d875f63f019dcd513762bb938a6 /rt/UPGRADING.mysql | |
parent | 6a79fae0c14b6635c67b4f224ee4a14f263b37d0 (diff) | |
parent | fc6209f398899f0211cfcedeb81a3cd65e04a941 (diff) |
This commit was generated by cvs2svn to compensate for changes in r10640,
which included commits to RCS files with non-trunk default branches.
Diffstat (limited to 'rt/UPGRADING.mysql')
-rw-r--r-- | rt/UPGRADING.mysql | 5 |
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. |