Bug #68210 creating a mixed case table with `lower_case_table_names` set to 1
Submitted: 28 Jan 2013 23:02 Modified: 9 Jul 2013 2:49
Reporter: Vince Eagen Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.44 CE rev 9933 OS:Windows (win 7 64bit)
Assigned to: CPU Architecture:Any
Tags: casing

[28 Jan 2013 23:02] Vince Eagen
Description:
When creating a table against a server with `lower_case_table_names` set to 1; the Object Browser shows the user entered casing instead of what is actually created in the database.

How to repeat:
1. set `lower_case_table_names` to 1
2. with MySQL Workbench create a table named `myTable`
3. observe the capital 'T' in myTable in the Object Browser
4. press ctrl-t for a new sql tab and run: "show tables;"
5. observe the actual case of the table name

Suggested fix:
after creating a table; pull the generated name and case from the db

consider warning the user if they use mixed case with a `lower_case_table_names` setting that would cause their entry to not be identical

test subsequent alter tables
[28 Jan 2013 23:03] Vince Eagen
casing difference on same screen

Attachment: bug68210-table-casing.png (image/png, text), 29.26 KiB.

[22 Feb 2013 21:59] Ruben Dario Morquecho Valdez
window7
Workbench 5.2.47 
---------
bug reproduced .

Being verified
[20 Jun 2013 19:09] Alfredo Kojima
Posted by developer:
 
Proper handling and warning for lower_case_table_names=1 was added in live table creation
[9 Jul 2013 0:08] Philip Olson
Fixed as of MySQL Workbench 6.0.3 (BETA 2), and here's the changelog entry:

After creating a table against a MySQL server with
"lower_case_table_names" enabled, the "Object Browser" would display the
new table name as the user entered it, instead of displaying how it was
created with lower-case. The lowercase version is now displayed, and the
user is notified of the conversion.

Thank you for the bug report.
[9 Jul 2013 2:49] Vince Eagen
Thank you for the timely fix.