MySQL Bugs: #6371: Character set option for backup

Bug #6371	Character set option for backup
Submitted:	1 Nov 2004 20:09	Modified:	24 Mar 2009 14:59
Reporter:	Shuichi Tamagawa	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Administrator	Severity:	S4 (Feature request)
Version:	1.2.14	OS:	Windows (Win XP / SP2)
Assigned to:		CPU Architecture:	Any

Description:
Currently the SQL dump file created by MySQL Administrator is encoded in utf8 with no choice. However, there are some mis-mapped and incompatible characters between sjis(ujis) and utf8. As a result the table data after restoring the backup file can be inconsistent with the original one. So users should be able to choose the character set in 'Advanced Option' tab so that they can specify the character set of backup file which is the same as the table character set.

Exapmle:
0x5C becomes 0x815F after restoring because of mis-mapping
0x878A becomes 0x3F after restoring because of incompatibility

How to repeat:
N/A

Suggested fix:
N/A

Many thanks for writing a feature request.

This is related to bug #37610 and bug #30946.

This is in progress for MySQL 6.0.

I think we should have a user choose for file encoding at every backup/restore possibility that we offer. Including backup/restore at MySQL Administrator.

Many thanks for writing a bug report. We are on the way to implement full functionality of MySQL Administrator into MySQL Workbench. We won't add this feature request anymore.

More informations about MySQL Workbench you will find here:

http://dev.mysql.com/workbench/