Bug #10299 The "Table Editor" does not apply changes if just the case was modified
Submitted: 1 May 2005 22:05 Modified: 31 May 2005 18:37
Reporter: [ name withheld ] Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Query Browser Severity:S3 (Non-critical)
Version:1.1.7 OS:Linux (Linux/Debian)
Assigned to: Vladimir Kolesnikov CPU Architecture:Any

[1 May 2005 22:05] [ name withheld ]
Description:
From: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=296463

Expected behavior:
The click on "Apply Changes" should rename the table, even if only the 
case changed. The MySQL DB seems to support that without problems.

Notes:
Almost the same problem apears in the "Table Editor" of the program 
"mysql-admin" (Package: mysql-admin, Version: 1.0.19-1).

How to repeat:
Steps to reproduce:
1. Start the query browser and connect to a mysql-server
2. In the sidebar "Schemata" open a schema, and navigate to one of its 
tables (let's call it "foobar")
3. Right-click on the table, and select "Edit..." from the context-menu, 
which yields a new window called "Table Editor"
4. Change the contents of the field labeled "Table Name". The changes 
should only affect the case of the "Table Name". That is, a case 
insensitive compare between the old and the new value should consider 
them equal. E.g. change "foobar" to "FooBar".. You may also change the case
of column names.
5. Don't do any other changes in the "Table Editor", and click the
"Apply Changes" button
6. A message window labeled "Information" pops up, saying "No 
modifications to be applied."

Suggested fix:
Workaround:
It is in fact possible to change just the case of a table name in the 
"TableEditor":
1. Change the table name thoroughly, not just the case.
2. Click the "Apply Changes" button.
3. An SQL script apears in a new window. Edit the "RENAME TO" part, so 
that it contains the desired table name.
4. Click "Execute". A confirmation message window apears. Now the talbe 
name is changed, even if only the case is different.
5. The "Table Editor" is not valid anymore, since it does not know about 
the correct new table name. An error message window pops up stating that 
problem. (This does not seem to be a real bug itself.)
6. Click "OK" and ignore it. Then click close in the "TableEditor".
[31 May 2005 18:37] Vladimir Kolesnikov
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