Hummm ... Thanks Ross.
Thinking about this then, if MS-SQL and Oracle force Uppercase, and if I want the code to work most easily across different backends then perhaps I should let it be the default values...
and let the drivers... in this case ColdFusion lowercase everything for me...
and if I use Oracle in the future CF will uppercase them for me... (True Statement ?) if true then I'm off and running again.
Thanks for the feedback.
At 06:01 PM 7/6/01 -0500, Ross J. Reedstrom wrote:
>On Fri, Jul 06, 2001 at 12:49:16PM -0700, Daniel Clark wrote:
>> Hi all,
>> A very newbie question...
>> Just started using ColdFusion5.0(Linux) against pgSQL(Linux7.1) using ODBC
>> It seems that ColdFusion sends along LowerCase TableNames and ColumnNames to pgSQL even if I program the .cfm files with MixedCase strings
>> The result is failure to locate tables and columns until I rename them in all lowercase.
>> Is there some feature in pgSQL that can make it insensitive to case in tablenames and column names?
>This is a required feature of ANSI SQL: case insensitivity. PostgreSQL
>implements this by downcasing all identifiers (Oracle, and MS-SQL,
>UPCASE EVERYTHING), unless they're quoted. I'm guessing your using some
>tool to create your MixedCase tablenames, and it's quoting them for you
>behind your back.
>So, either lose the quotes on the identifiers when you create the schema
>(i.e., let them get down cased) or write all your CF like so:
>select "SomeColumn"."SomeTable", "SomeOtherColumn"."SomeOtherTable" from
>P.S. Yup, you have to quote each identifier seperately, not the dotted
>identifier. Because, according to the standard, once you quote it,
>anything goes, so "This.is my Really Weird_column.name" is completely
In response to
pgsql-odbc by date
|Next:||From: Cedar Cox||Date: 2001-07-08 10:45:37|
|Subject: Re: ODBC 7.0006 bugs|
|Previous:||From: Ross J. Reedstrom||Date: 2001-07-06 23:01:16|
|Subject: Re: Cold Fusion to pgSQL|