[rt-users] RE: 3.6 to 3.6.1 server migration

[Mike Friedman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 18 Aug 2006 at 19:55 (-0400), Mathew Snyder wrote:

>> I haven't seen any documentation on the 'default binary' option, which 
>> is why I'm asking here.  If I ever have to restore one of my current 
>> backups, it would be nice to know that binary attachments weren't 
>> corrupted.
>> 
>> So, should I change my current dumps to use the binary option?
>
> The only thing I could recommend is to try it both with and without the 
> option during your testing before actually doing the migration.

Mathew,

I just tried specifying '--default-character-set=binary', but this wasn't 
accepted.  I got the following message instead of a dump:

    Usage: mysqldump [OPTIONS] database [tables]
    OR     mysqldump [OPTIONS] --databases [OPTIONS] DB1 [DB2 DB3...]
    OR     mysqldump [OPTIONS] --all-databases [OPTIONS]
    For more options, use mysqldump --help

This is mysql 5.0.22-1 on Linux (Fedora (FC5)).

In the mysql manual, although I see the '--default-character-set' option 
documented, there's no mention of 'binary' as a valid value.  What am I 
missing here?

Thanks.

Mike

_________________________________________________________________________
Mike Friedman                        IST/System and Network Security
mikef at berkeley.edu                   2484 Shattuck Avenue
1-510-642-1410                       University of California at Berkeley
http://socrates.berkeley.edu/~mikef  http://security.berkeley.edu
_________________________________________________________________________

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQA/AwUBROnbua0bf1iNr4mCEQJaUQCgjj4+7Xheq9hfqq90EvNYnHOWiRwAoO2p
9i1HlqrsThxQf6QTdD6edUAW
=EzsR
-----END PGP SIGNATURE-----