Bug #41266 | rename group fails if the new name differs only in case from existing name | ||
---|---|---|---|
Submitted: | 5 Dec 2008 15:36 | Modified: | 14 Jan 2009 15:19 |
Reporter: | Carsten Segieth | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Enterprise Monitor: Web | Severity: | S3 (Non-critical) |
Version: | 2.0.0.7119 | OS: | Any |
Assigned to: | Darren Oldag | CPU Architecture: | Any |
[5 Dec 2008 15:36]
Carsten Segieth
[5 Dec 2008 15:37]
Carsten Segieth
work around: rename in 2 steps (first add any char, then change to the wanted new name)
[5 Dec 2008 17:29]
Darren Oldag
the UI was prechecking for group existence, but did not consider group names case in a case insensitive manner. tests were added at the UI, business, and persistence layers to ensure we could rename groups to a different case. committed to trunk. awaiting review for push into 2.0 GA or 2.0.1 maintenance.
[16 Dec 2008 19:01]
Darren Oldag
pushed to 2.0 maintenance branch, awaiting build.
[18 Dec 2008 15:43]
Carsten Segieth
tested OK in 2.0.2.7126
[14 Jan 2009 15:19]
Tony Bedford
An entry was added to the 2.0 changelog: The Rename Group function failed if the new group name was different to the current one only in the case used; for example, if “Merlin” was changed to “MERLIN”. The error generated was: U0105 This group name is already in use. Enter a different name.