[Rt-commit] rt branch, 4.0/backup-docs, updated. rt-4.0.7-59-gfa19eb5

[Thomas Sibley]

The branch, 4.0/backup-docs has been updated
       via  fa19eb5d4ab1ae2371abcc65c941742c4efb9e01 (commit)
      from  e8e95b66d148c4fdbb89944cb2ab2b24f361d45b (commit)

Summary of changes:
 docs/backups.pod | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

- Log -----------------------------------------------------------------
commit fa19eb5d4ab1ae2371abcc65c941742c4efb9e01
Author: Thomas Sibley <trs at bestpractical.com>
Date:   Fri Nov 2 14:50:09 2012 -0700

    Note when to use --default-character-set=binary for MySQL backups
    
    Clarifies the subject of the following paragraph since it's now
    separated from the command example.

diff --git a/docs/backups.pod b/docs/backups.pod
index a5d9083..2dab6f0 100644
--- a/docs/backups.pod
+++ b/docs/backups.pod
@@ -35,8 +35,12 @@ RT. :)
     mysqldump rt4 --ignore-table rt4.sessions \
                   --single-transaction | gzip > rt-`date +%Y%M%d`.sql.gz
 
-It will be much faster if you can connect to the MySQL server over localhost.
-This will use a local socket instead of the network.
+If you're using a MySQL version older than 4.1.2 (only supported on RT 3.8.x
+and older), you should be also pass the C<--default-character-set=binary>
+option to the second C<mysqldump> command.
+
+The dump will be much faster if you can connect to the MySQL server over
+localhost.  This will use a local socket instead of the network.
 
 If you find your backups taking far far too long to complete (this point should
 take quite a long time to get to on an RT database), there are some alternate

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