Table name "case sensitivity"

I am still quite new to MySQL, so this is definately a "newbie"
question.

I have loaded MySQL on my WinXP system to use as a test/development
platform. Our "live" system is SUSE 10.1 Linux with MySQL.
Connection between servers is simply a matter of changing the DSN name
in the code (using ooRexx and Rexx/SQL for my programming).

Many of the MySQL tables are being created through an automated
process I developed to extract data from BTrieve databases. Some of
these databases' "dictionary" files are in upper case and some in
lower case (BTrieve dictionaries are basically schemas). Since my
automation process simply uses the dictionary name as the table name,
the result is that some are in upper case and some in lower case.

I know Linux is much more case sensitive that Windows, but does anyone
know if this is going to cause "headaches" down the road? Would I be
better off to modify my automation script to "force" the case to be
one or the other, and if so, which case would you recommend?

Thanks,
Lee

Lee Peedin wrote:
> I am still quite new to MySQL, so this is definately a "newbie"
> question.
>
> I have loaded MySQL on my WinXP system to use as a test/development
> platform. Our "live" system is SUSE 10.1 Linux with MySQL.
> Connection between servers is simply a matter of changing the DSN name
> in the code (using ooRexx and Rexx/SQL for my programming).
>
> Many of the MySQL tables are being created through an automated
> process I developed to extract data from BTrieve databases. Some of
> these databases' "dictionary" files are in upper case and some in
> lower case (BTrieve dictionaries are basically schemas). Since my
> automation process simply uses the dictionary name as the table name,
> the result is that some are in upper case and some in lower case.
>
> I know Linux is much more case sensitive that Windows, but does anyone
> know if this is going to cause "headaches" down the road? Would I be
> better off to modify my automation script to "force" the case to be
> one or the other, and if so, which case would you recommend?
>
> Thanks,
> Lee
>
>

It can. Table names are case sensitive in Unix but now Windows.

Just be careful and use the same convention throughout. Which
convention you use is up to you.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

On Fri, 27 Oct 2006 08:09:51 -0400, Jerry Stuckle
<jstucklex@attglobal.net> wrote:

>Lee Peedin wrote:
>> I am still quite new to MySQL, so this is definately a "newbie"
>> question.
>>
>> I have loaded MySQL on my WinXP system to use as a test/development
>> platform. Our "live" system is SUSE 10.1 Linux with MySQL.
>> Connection between servers is simply a matter of changing the DSN name
>> in the code (using ooRexx and Rexx/SQL for my programming).
>>
>> Many of the MySQL tables are being created through an automated
>> process I developed to extract data from BTrieve databases. Some of
>> these databases' "dictionary" files are in upper case and some in
>> lower case (BTrieve dictionaries are basically schemas). Since my
>> automation process simply uses the dictionary name as the table name,
>> the result is that some are in upper case and some in lower case.
>>
>> I know Linux is much more case sensitive that Windows, but does anyone
>> know if this is going to cause "headaches" down the road? Would I be
>> better off to modify my automation script to "force" the case to be
>> one or the other, and if so, which case would you recommend?
>>
>> Thanks,
>> Lee
>>
>>
>
>It can. Table names are case sensitive in Unix but now Windows.
>
>Just be careful and use the same convention throughout. Which
>convention you use is up to you.


Thanks Jerry,
I kinda suspected that. :-)

Lee

Lee

Rather than mucking about with your conversion. When I ported my DB from XP
to AIX I just set up the file /etc/my.cfg to include

[mysqld]
lower-case-table-names=1

and for me this did the trick.

Rob
"Lee Peedin" <lpeedinDONOTSPAME@nc.rr.com> wrote in message
news:pbu3k25tas8abthoo4f9u3id8qqo206k8j@4ax.com...
> On Fri, 27 Oct 2006 08:09:51 -0400, Jerry Stuckle
> <jstucklex@attglobal.net> wrote:
>
>>Lee Peedin wrote:
>>> I am still quite new to MySQL, so this is definately a "newbie"
>>> question.
>>>
>>> I have loaded MySQL on my WinXP system to use as a test/development
>>> platform. Our "live" system is SUSE 10.1 Linux with MySQL.
>>> Connection between servers is simply a matter of changing the DSN name
>>> in the code (using ooRexx and Rexx/SQL for my programming).
>>>
>>> Many of the MySQL tables are being created through an automated
>>> process I developed to extract data from BTrieve databases. Some of
>>> these databases' "dictionary" files are in upper case and some in
>>> lower case (BTrieve dictionaries are basically schemas). Since my
>>> automation process simply uses the dictionary name as the table name,
>>> the result is that some are in upper case and some in lower case.
>>>
>>> I know Linux is much more case sensitive that Windows, but does anyone
>>> know if this is going to cause "headaches" down the road? Would I be
>>> better off to modify my automation script to "force" the case to be
>>> one or the other, and if so, which case would you recommend?
>>>
>>> Thanks,
>>> Lee
>>>
>>>
>>
>>It can. Table names are case sensitive in Unix but now Windows.
>>
>>Just be careful and use the same convention throughout. Which
>>convention you use is up to you.
>
>
> Thanks Jerry,
> I kinda suspected that. :-)
>
> Lee

On Fri, 27 Oct 2006 15:33:26 +0100, "LittleRob"
<greeneggsandham@gretmouse.co.uk> wrote:

>Lee
>
>Rather than mucking about with your conversion. When I ported my DB from XP
>to AIX I just set up the file /etc/my.cfg to include
>
>[mysqld]
>lower-case-table-names=1
>
>and for me this did the trick.
>
>Rob

Rob,
You da man - thanks for this tip!

Lee

> Rather than mucking about with your conversion. When I ported my DB from XP
> to AIX I just set up the file /etc/my.cfg to include
>
> [mysqld]
> lower-case-table-names=1


I always set it to 2 for windows, so it stores the names in a case
sensitive manner. Windows will still not be case sensitive, though.
Inconsistencies across platforms are easily found with unit tests and
error logging.

Best regards