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: | |
Category: | MySQL Query Browser | Severity: | S2 (Serious) |
Version: | 1.1.2 | OS: | Windows (Windows XP (SP2)) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[29 Dec 2004 8:53]
Chris Pete
[3 Jan 2005 17:30]
Michael G. Zinner
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.
[14 Feb 2005 22:54]
Bugs System
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".