From: | Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl> |
---|---|
To: | Nico Sabbi <nsabbi(at)officinedigitali(dot)it> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: case dumbiness in return from functions |
Date: | 2008-01-18 12:42:50 |
Message-ID: | 485D882F-C087-4DAD-A2DC-EA4B49032678@solfertje.student.utwente.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Jan 18, 2008, at 1:14 PM, Nico Sabbi wrote:
> Tom Lane ha scritto:
>> The SQL standard specifies that unquoted identifiers are case-
>> insensitive.
^^^^^^^^
>> You're welcome to spell them as camelCase in your source code if you
>> feel like it, but don't expect that PG, or any other SQL-compliant
>> database, will pay attention.
>>
>> regards, tom lane
> yet I find disturbing that Postgres doesn't make the effort
> to respect the case specified by the user. If I created a field
> called "REF" why should Postgres call it "ref" in the output of
> queries
> if the standard doesn't specify any obligation to convert the name ?
If you want to use case sensitive identifiers, then quote them! It's
not that hard. In your example above you're doing just that, so your
statement does not even apply ;)
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,47909a669491882451502!
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2008-01-18 12:43:08 | Re: case dumbiness in return from functions |
Previous Message | Gregory Williamson | 2008-01-18 12:39:16 | Re: case dumbiness in return from functions |