MySQL Bugs: #7208: problem restoring DB when char set encoding unknown

Bug #7208	problem restoring DB when char set encoding unknown
Submitted:	12 Dec 2004 20:39	Modified:	17 Dec 2004 0:23
Reporter:	mike wilson	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.0.17	OS:	Windows (XP Home SP2)
Assigned to:	Victor Vagin	CPU Architecture:	Any

Description:
I had problems restoring an entire database because I didn't know the encoding
and I have three problems/potential "bugs".

I know "seperate bug report for each bug" but they are related and may not be bugs due to operator error, i.e me.

1) Better encoding type detection.  "AutoDetect char set" couldn't find the correct char set; it was latin1 but how hard is it to determine that?

2) No informative message when retore doesn't work. The char set defaulted to utf8 so I clicked "Start Retore".  A small window pops up saying it was Analyzing the file.  "Total Number of Bytes: 0" "Number of Bytes processed: 0" and a blank progress bar. At 1st I thought it was working on the file but then I realised it was done with nothing processed.  A (better?) message that it had failed to restore anything and was finished would be nice.

3) Put encoding used into backup file.  Since utf8 didn't work I guessed latin1 and got lucky.  The comment in the backup file said it was from MySQL 4.0.18 so maybe things have changd since then, but it sucks having to guess the encoding.   

thanks

mike w.
 

How to repeat:
perform a restore and pick the the wrong char set type

Thank you for your bug report. This issue has already been fixed
in the latest released version of that product, which you can download at 
http://www.mysql.com/downloads/