Bug #9731 | lower-case-table-names does not work as expected/documented | ||
---|---|---|---|
Submitted: | 7 Apr 2005 21:02 | Modified: | 8 May 2005 21:09 |
Reporter: | Raymond DeRoo | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 4.1.11 | OS: | Windows (Windows) |
Assigned to: | CPU Architecture: | Any |
[7 Apr 2005 21:02]
Raymond DeRoo
[7 Apr 2005 21:21]
MySQL Verification Team
c:\mysql\bin>mysql -uroot ray Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 to server version: 4.1.11-nt Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> create table UmYhT (id int); Query OK, 0 rows affected (0.08 sec) mysql> show tables; +---------------+ | Tables_in_ray | +---------------+ | umyht | +---------------+ 1 row in set (0.00 sec) mysql> show variables like "%case%"; +------------------------+-------+ | Variable_name | Value | +------------------------+-------+ | lower_case_file_system | OFF | | lower_case_table_names | 1 | +------------------------+-------+ 2 rows in set (0.00 sec) mysql> exit Bye c:\mysql\bin>mysqladmin shutdown -uroot c:\mysql\bin>mysql -uroot ray Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 to server version: 4.1.11-nt Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> create table MMnnMM (id int); Query OK, 0 rows affected (0.08 sec) mysql> show variables like "%case%"; +------------------------+-------+ | Variable_name | Value | +------------------------+-------+ | lower_case_file_system | ON | | lower_case_table_names | 2 | +------------------------+-------+ 2 rows in set (0.00 sec) mysql> show tables; +---------------+ | Tables_in_ray | +---------------+ | MMnnMM | | umyht | +---------------+ 2 rows in set (0.00 sec) mysql>
[8 Apr 2005 21:09]
Sergei Golubchik
Looks like a duplicate of http://bugs.mysql.com/9761
[8 May 2005 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".