Bug #12655 | Not all Usernames are possible | ||
---|---|---|---|
Submitted: | 18 Aug 2005 17:51 | Modified: | 26 Sep 2005 15:28 |
Reporter: | David Quirós | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Query Browser | Severity: | S2 (Serious) |
Version: | 1.1.13 | OS: | Windows (Windows XP) |
Assigned to: | Mike Lischke | CPU Architecture: | Any |
[18 Aug 2005 17:51]
David Quirós
[26 Aug 2005 7:43]
Andrey Ryskov
yes, got the same username - in russian
[26 Aug 2005 9:16]
Valeriy Kravchuk
I was able to reproduce exactly the described behaviour on (Russian) XP with russian user name. I had created a new user with name in Russian (not a good idea, but why not). Logged in (there were no QB in Start menu, by the way). Then started QB manually. It was started without any problems. There were no messages when I saved options (the connection parameters), but upon next startup I've got the described error messages. Will upload a screenshot of one... After that, I was able to enter connection options again.
[26 Aug 2005 9:18]
Valeriy Kravchuk
The first error message displayed
Attachment: qb_xml_bug.PNG (image/png, text), 13.43 KiB.
[29 Aug 2005 8:43]
Sören Andersson
I have the same problem. But with a scandinavian charachter in the username in the Windows XP. åöä. The only way to get Mysql Browser working is to delete all xml files in the Applcation Data/Mysql folder. I saw this bug already in a early version of Mysql Query Browser.
[29 Aug 2005 8:49]
Sören Andersson
Suggested fix: Change how you load the xml option files to the mysql browser. It looks like the mysql query browser xml file loader doesnt support charachter sets like scandinavian, russian.... in the path to the xml files. ---->\Sören\Application Data\MySQL
[26 Sep 2005 15:28]
Mike Lischke
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. If necessary, you can access the source repository and build the latest available version, including the bugfix, yourself. More information about accessing the source trees is available at http://www.mysql.com/doc/en/Installing_source_tree.html