I noticed later builds of Drizzle basically have the equivalent of lower_case_table_names=1 with no way to reverse the affect?
drizzle> create database Test; Query OK, 1 row affected (0.01 sec) drizzle> show databases; +--------------------+ | Database | +--------------------+ | DATA_DICTIONARY | | INFORMATION_SCHEMA | | mcptest | | Test | +--------------------+ 4 rows in set (0 sec) drizzle> use Test; Database changed drizzle> create table T1 (num1 serial); Query OK, 0 rows affected (0.06 sec) drizzle> show tables; +----------------+ | Tables_in_Test | +----------------+ | t1 | +----------------+ 1 row in set (0 sec) What I find weird about this is that the "Test" database has a 'test' folder in the 'local' directory. So Drizzle knows what case I originally used for databases. Why not tables? Any reasoning behind this? I much prefer to use mixed case in my table names and while I can still do that on the application side, using the drizzle command-line forces the lower case and makes things a bit harder to wade through. _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
