Further examination of the documents reveals a variable that addresses this... I fixed it with this entry in my.cnf:
set-variable = lower_case_table_name=0 According to the MySQL manual lower_case_table_name defaults to 0 for all instances except Windows, where it defaults to 1... Not clear why this instance was behaving as if it was set to 1. Best Regards, Bruce On 9/25/03 11:27 PM, "Bruce Dembecki" <[EMAIL PROTECTED]> wrote: > Hi. We are migrating our Solaris setup to an OSX server. I used InnoDB Hot > Backup to copy the InnoDB files, and copied the .frm files for each of the > databases. > > Under OSX I connect top the server and it sees the databases. If I use > some_database where some_database has mixed case table names I see errors such > as this: > > mysql> use some_database > Reading table information for completion of table and column names > You can turn off this feature to get a quicker startup with -A > > Didn't find any fields in table 'deletedForum' > Didn't find any fields in table 'deletedForumProp' > Didn't find any fields in table 'deletedMessage' > Didn't find any fields in table 'deletedMessageProp' > > If I "show tables;" I get a list such as this: > > mysql> show tables; > +-------------------------+ > | Tables_in_some_database | > +-------------------------+ > | deletedForum | > | deletedForumProp | > | deletedMessage | > | deletedMessageProp | > > > If I try to select data in a field I get errors such as this: > > mysql> select * from deletedMessage; > ERROR 1146: Table 'some_database.deletedmessage' doesn't exist > > If I "show table status;" I get information such as this (sorry, this is going > to be messy - but you get the idea): > > mysql> show table status; > +---------------------+------+------------+------+----------------+----------- > --+-----------------+--------------+-----------+----------------+------------- > +-------------+------------+----------------+--------------------------------- > -----------------------+ > | Name | Type | Row_format | Rows | Avg_row_length | > Data_length | Max_data_length | Index_length | Data_free | Auto_increment | > Create_time | Update_time | Check_time | Create_options | Comment > | > +---------------------+------+------------+------+----------------+----------- > --+-----------------+--------------+-----------+----------------+------------- > +-------------+------------+----------------+--------------------------------- > -----------------------+ > | deletedForum | NULL | NULL | NULL | NULL | > NULL | NULL | NULL | NULL | NULL | NULL > | NULL | NULL | NULL | Table > 'some_database.deletedforum' doesn't exist | > | deletedForumProp | NULL | NULL | NULL | NULL | > NULL | NULL | NULL | NULL | NULL | NULL > | NULL | NULL | NULL | Table > 'some_database.deletedforumprop' doesn't exist | > | deletedMessage | NULL | NULL | NULL | NULL | > NULL | NULL | NULL | NULL | NULL | NULL > | NULL | NULL | NULL | Table > 'some_database.deletedmessage' doesn't exist | > | deletedMessageProp | NULL | NULL | NULL | NULL | > NULL | NULL | NULL | NULL | NULL | NULL > | NULL | NULL | NULL | Table > 'some_database.deletedmessageprop' doesn't exist | > > > In another database which has only lower case table names I have no problems > and all works well. Given I ask to select data from deletedMessage and it > tells me there is no table .deletedmessage something somewhere dropped the > uppercase in the table name... > > The idea of making all the table names lower case isn't a good one, there are > 50+ databases, with 40+ tables each, and over 100 applications that call these > databases all with innumerable table calls. > > I don't know if it's an InnoDB issue, an OSX issue or what's going on or how I > might solve it. I don't seem to see anything on the list archive about this. > Any ideas? > > Best Regards, Bruce -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
