I saw the change as soon as it was posted last week or whenever and
didn't think anything of it. But the point Yves brings up seems very
Although, I'm not sure what to do then with "bug #1812." Too bad MySQL's
code can't make database/table names case-sensitive like on *nix. e.g.
*Force* the case used in queries match that of the directory/file
----- Original Message -----
From: "Reverend Deuce"
Sent: Wednesday, December 17, 2003 3:41 PM
Subject: Re: MySQL 4.0.17 has been released
> I agree, 100%. We live in a mixed environment of UNIX and Windows and
> such, we've assumed case insensitivity in our apps. I know that this
> 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. :(
> -- R
> ----- Original Message -----
> From: "Yves Goergen"
> 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
> > that I cannot create tables only differing by case of the name, but
> > to have this setting off to be able to dump my tables on Windows
> > 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
> > my application couldn't find its tables anymore (as
> > 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