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 webhoster's Linux server. If the setting was enabled, I'd get all wrong table names and my application couldn't find its tables anymore (as 'bb1_GroupMembers' gets 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 [EMAIL PROTECTED] 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/[EMAIL PROTECTED]
Re: MySQL 4.0.17 has been released
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. :( -- R - Original Message - From: Yves Goergen [EMAIL PROTECTED] To: Lenz Grimmer [EMAIL PROTECTED]; [EMAIL PROTECTED] 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 webhoster's Linux server. If the setting was enabled, I'd get all wrong table names and my application couldn't find its tables anymore (as 'bb1_GroupMembers' gets 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 [EMAIL PROTECTED] 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/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 4.0.17 has been released
Hi! I would like to remind people that if you want to move an InnoDB database between Unix and Windows, you have to consider the following: http://www.innodb.com/ibman.php#Moving On Windows InnoDB stores the database names and table names internally always in lower case. To move databases in a binary format from Unix to Windows or from Windows to Unix you should have all table and database names in lower case. A convenient way to accomplish this is to add on Unix the line set-variable=lower_case_table_names=1 to the [mysqld] section of your my.cnf before you start creating your tables. On Windows the setting 1 is the default. That is, the best solution for portability is to have the database and table names always in lower case. Setting globally set-variable=lower_case_table_names=1 is a convenient way to accomplish this. Best regards, Heikki Tuuri Innobase Oy http://www.innodb.com Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - hot backup tool for InnoDB which also backs up MyISAM tables Order MySQL technical support from https://order.mysql.com/ - Original Message - From: Reverend Deuce [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Wednesday, December 17, 2003 11:42 PM Subject: Re: MySQL 4.0.17 has been released 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. :( -- R - Original Message - From: Yves Goergen [EMAIL PROTECTED] To: Lenz Grimmer [EMAIL PROTECTED]; [EMAIL PROTECTED] 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 webhoster's Linux server. If the setting was enabled, I'd get all wrong table names and my application couldn't find its tables anymore (as 'bb1_GroupMembers' gets 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 [EMAIL PROTECTED] 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/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 4.0.17 has been released
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 - 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 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. :( -- 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 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 webhoster's Linux server. If the setting was enabled, I'd get all wrong table names and my application couldn't find its tables anymore (as 'bb1_GroupMembers' gets 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? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 4.0.17 has been released
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 [EMAIL PROTECTED] 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 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 4.0.17 has been released
Hi! Well, I checked the code and looks like in 4.0.17 lower_case_table_names is NOT forced to 1 on case-insensitive file system, despite the changelog entry (that we will fix, by the way). Obviously a programming mistake, but for now only warning that lower_case_table_names is forced to 1 is issued, no actual assignement takes place. I think, as there are users that need lower_case_table_names=0 on Windows, we could set the *default* value based on filesystem case-sensitivity, but with the possibility to change it from the command line, and issue a BIG RED WARNING if you'll do. So don't do it unless you know what you are doing. To quote Monty: The 'bug' here is that if you set lower_case_table_names to OFF on a system where you have case insensitive file names (like windows) you WILL get table corruption if you access tables with different cases. This is becasue MySQL doesn't know that the tables 'name' and 'NAME' are in fact the same table and will cache and lock each of these separately. On Dec 17, Reverend Deuce wrote: 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. :( -- R - Original Message - From: Yves Goergen [EMAIL PROTECTED] To: Lenz Grimmer [EMAIL PROTECTED]; [EMAIL PROTECTED] 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 webhoster's Linux server. If the setting was enabled, I'd get all wrong table names and my application couldn't find its tables anymore (as 'bb1_GroupMembers' gets 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? Regards, Sergei -- __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Senior Software Developer /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
