List:General Discussion« Previous MessageNext Message »
From:Yves Goergen Date:December 17 2003 11:54pm
Subject:Re: MySQL 4.0.17 has been released
View as plain text  
OK, ehm, considering Heikki's post, why does MySQL take care of
case-sensitive table names at all? I'm not that familiar with the whole
thing about it, but aren't database names also case-insensitive? I know that
column names are. So why isn't this option removed and table names are
generally treated case-insensitive? (E.g. forcing lowercase_tablenames=1
anywhere.) This won't resolve the problems with older database servers
though, as long as I have no chance to change the lowercase_tablenames
setting (BTW, can I change this per connection?), but in future, this
problem could be avoided.

-- 
Yves Goergen
nospam.list@stripped
Please don't CC me (causes double mails)


On Wednesday, December 17, 2003 11:37 PM CET, Matt W wrote:
> Hi,
>
> 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
> important!
>
> 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 name...
>
>
> Matt

Thread
mysqltopThomas Wana13 Mar
  • Re: mysqltopJim Faucette13 Mar
  • Re: MySQL 4.0.17 has been releasedYves Goergen17 Dec
  • Re: MySQL 4.0.17 has been releasedReverend Deuce17 Dec
    • Re: MySQL 4.0.17 has been releasedSergei Golubchik18 Dec
  • Re: MySQL 4.0.17 has been releasedMatt W17 Dec
  • Re: MySQL 4.0.17 has been releasedYves Goergen18 Dec
Re: MySQL 4.0.17 has been releasedHeikki Tuuri17 Dec