MySQL Bugs: #7567: Umlauts not supported as database names

Bug #7567	Umlauts not supported as database names
Submitted:	29 Dec 2004 8:53	Modified:	3 Feb 2005 17:30
Reporter:	Chris Pete	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S2 (Serious)
Version:	1.1.2	OS:	Windows (Windows XP (SP2))
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
When using umlauts (ä, ö, ü) in database names MySQL Query Browser (1.1.2) is not able to "open" this database and perform "select"s etc. There's, in fact, no problem when doing "select"s using TABLE names with umlauts.

How to repeat:
Create a table using umlauts (ä,ö,ü) and a sample table with contents. Then try to do a "select * from" from this table (after selecting the umlauts-DB first).

Suggested fix:
Despite the fact that using umlauts in database names and tables is not the suggested way to go (obviously), there is nothing I could do to change it in our company as many scripts / programs access them this way. Changing it would cause massive damage (since there are many external developers involved). The fix I would suggest is checking the Query Browser for this problem... I can assure that MySQL specific user rights had nothing to do with it.

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/

Additional info:

If you upgrade QB to 1.1.4 and your server to 4.1.8 the problem should be gone since we addressed an UTF8 issue in the server that now allows the GUI tools to use a better non-latin1 character handling.

If you are talking about "Umlauts" you mean the German Umlauts, right? I wonder what the problem is in your case, since we always test with latin1 characters and a database named ´ärger´ was supposed to work from the start.

Could you check your collation settings of the server and the database you are using? You can do this with 

show variables;

which should give an output like 
'collation_connection', 'latin1_swedish_ci'
'collation_database', 'latin1_swedish_ci'
'collation_server', 'latin1_swedish_ci'

and 

show create database `test`;

'test', 'CREATE DATABASE `test` /*!40100 DEFAULT CHARACTER SET latin1 */'

Please report if this works for you.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".