I agree, 100%. We live in a mixed environment of UNIX and Windows and as
such, we've assumed case insensitivity in our apps. I know that this is bad
practice, but forcing this flag on us is and even worse practice. This
should always, always be an option.
I wont be able to upgrade until this is fixed. :(
----- Original Message -----
From: "Yves Goergen" <nospam.list@stripped>
To: "Lenz Grimmer" <lenz@stripped>; <mysql@stripped>
Sent: Wednesday, December 17, 2003 1:12 PM
Subject: Re: MySQL 4.0.17 has been released
> On Wednesday, December 17, 2003 1:58 PM CET, Lenz Grimmer wrote:
> > Functionality added or changed:
> > * `lower_case_table_names' is now forced to 1 if the database
> > directory is located on a case-insensitive file system. (Bug
> > #1812)
> Uh, _very_ bad. I know that my Windows filesystem is case-insensitive and
> that I cannot create tables only differing by case of the name, but I need
> to have this setting off to be able to dump my tables on Windows with the
> correct (and not lower-cased!!) table names to import them on my
> Linux server. If the setting was enabled, I'd get all wrong table names
> my application couldn't find its tables anymore (as 'bb1_GroupMembers'
> to 'bb1_groupmembers' and that's something else!).
> So please change this back again, I believe it's up to the server
> administrator to set this in a correct and reasonable way, don't you?
> Yves Goergen
> Please don't CC me (causes double mails)
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1