Bug #7020 mysqldump --compatible=mysql40 should set --skip-set-charset --default-char...
Submitted: 5 Dec 2004 15:41 Modified: 22 Dec 2004 13:07
Reporter: Timothy Smith
Status: Closed
Category:Client Severity:S3 (Non-critical)
Version:4.1.7 OS:Any (all)
Assigned to: Alexander Barkov Target Version:

[5 Dec 2004 15:41] Timothy Smith 
Description:
mysqldump --compatible=mysql40 still dumps data in the utf8 character set.

It would be most compatible if that switch forced mysqldump to add --skip-set-charset and
--default-character-set=<default charset of server/database>.

How to repeat:
See description.

Suggested fix:
See description.
[22 Dec 2004 13:07] Alexander Barkov 
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Fixed in 4.1.9