On 24/10/2007, at 9:31 AM, Walden H. Leverich wrote:

I have simply quoted them ALL as a matter of course.

I think the problem here is that the entries on the table were created
in mixed-case using "" therefore all subsequent references to the long
names must match case.

Exactly.


I'm sorry, but this is ridiculous! Effectively we're saying you can't
create a mixed case column name under i5/OS, because if you do you will
be forced to refer to that column in the exact same casing you create
it. And, AFAIK, SQL is NOT a case sensitive language! So what was IBM
thinking?

I don't know whether the SQL standard says SQL is case-insensitive. Should be easy enough to verify. I suspect the language itself is case-insensitive but it has to cope with object and column naming conventions of the database.

I do know that the system (i.e., IBM) is honouring the creation request. If the creator simply typed the name in unquoted it will be mono-cased by SQL. If the creator quoted the name then SQL honours that and does not change it (via mono-case).

If you don't like the case-sensitivity or cannot determine the proper case then simply use the short column names--although those can be less than helpful.

Seems to me this is behaving exactly as expected--certainly how I would expect it to behave. I can't speak about the behaviour of SQL on other platforms.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2021 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.