MySQL Bugs: #21268: mysqldump character set error

Bug #21268	mysqldump character set error
Submitted:	25 Jul 2006 8:54	Modified:	28 Aug 2006 10:27
Reporter:	Mickael Besson	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Administrator	Severity:	S2 (Serious)
Version:	1.2.2 beta	OS:	Windows (Windows 2000 Server / XP)
Assigned to:	Mike Lischke	CPU Architecture:	Any
Tags:	Backup

Description:
The program mysqldump doesn't format the SQL backup into good character set : utf8 by default

How to repeat:
1/Create a backup with mysqldump.
Example :
mysqldump --single-transaction --all-databases > backup_MYSQL.sql -u root -pPASSWORD

2/Try to analyse this backup with MySQL Administrator (Restore / Open Backup / Restore Content / Analyse Backup File Content)
-> "the analyzation failed"

3/open this backup SQL with Notepad
  save it with charset utf8

4/try again to analyse the backup with MySQL Administrator
-> It's OK now !

Suggested fix:
character set error in mysqldump tool

Thank you for the bug report. Looks to me that is an issue of MySQL
Administrator reading the backup file done by mysqldump, when restored
with mysql client not presents any issue:

c:\mysql\bin>mysqldump --single-transaction --all-databases > backup_MYSQL.sql -u root

c:\mysql\bin>mysql -uroot < backup_MYSQL.sql

c:\mysql\bin>

This error is still present in version 1.2.2 beta of MA.

Well, then GUI team does not maintain mysqldump so it is not up to us to fix any problem in it. Additionally, MA is usually only able to restore dumps which were made with it. In the new MA we have added a check that prevents users from restoring dumps, which were not created using MA, unless you switch on to ignore errors.

For the encoding problem: mysqldump creates latin 1 encoded files so you have to use this encoding when you open the dump in MA. Default ist utf-8 so this does not work well. To change this use the File Charset combobox on the general tab in the restore settings.