I would vote 'no'. It's nice in some cases, but I don't think it is necessary. I would like to know if table_name= file_name serves any necessary purpose, especially since changing it could provide benefits.
Patrick On Fri, Nov 12, 2010 at 5:41 PM, Andrew Hutchings <[email protected]>wrote: > Hi guys, > > I believe this has been brought up before but I want to refresh the topic. > > If we switch table filenames to be based on a unique ID instead of table > file name it can solve a few potential problems especially around case and > utf8 characters. > > Schema directory names would still be based on the schema name as > per-usual. > > What do you guys think? Is having the file name similar (there are cases > at the moment where it isn't exactly the same anyway) to the table name > important? > > Kind Regards > -- > Andrew Hutchings - LinuxJedi - http://www.linuxjedi.co.uk/ > > _______________________________________________ > Mailing list: > https://launchpad.net/~drizzle-discuss<https://launchpad.net/%7Edrizzle-discuss> > Post to : [email protected] > Unsubscribe : > https://launchpad.net/~drizzle-discuss<https://launchpad.net/%7Edrizzle-discuss> > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
