MySQL Bugs: #5440: Non case sensitive Schema Names

Bug #5440	Non case sensitive Schema Names
Submitted:	7 Sep 2004 8:07	Modified:	18 Oct 2004 11:12
Reporter:	Andras Fabian	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S2 (Serious)
Version:	1.0.12	OS:	Windows (Windows 2000)
Assigned to:	Victor Vagin	CPU Architecture:	Any

Description:
Recently we had to rename some of our DB's by changing their name from upper-/lower-Case-mix to lower-caseonly-only. Temporarily we had databases with the old and the new names. During this time I tryed to apply the same Schema rights to the new lower-caseonly-only DB but the MySQL Administrator never made the changes happene. Instead it chaged the rights for the upper-/lower-Case-mix DB but not for the new lower-caseonly-only DB.

How to repeat:
Create a Schema named "TEST". Then go to the User Administrator and assign some Schema Privileges to it (one user is enough). Then create a Schema named "test". Go to User Administrator and try to assign some Schema rights for the same user. After "Apply" the Schema "test" doesn't show any Schema rights, but instead the Schema "TEST" has the changes. It sometimes even seems to mix up completly the assigned rights. In one situation (I remember, I rtyed to remove the "ALTER" privilege from "TEST") it also gave an Error message like "MySQL Eror Nr. 1062 Duplicate entry '%-test-TestUse' for key 1"

Suggested fix:
It seems to me, that MySQL Administrator doesn't handle lower/upper case schema names correctly. But it should, as MySQL makes a difference between lower/upper case.

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