Brian T. Allen wrote:
> I just ran into that too, and find it most undesirable. I don't know
> whether that is part of the SQL spec or not, but it seems very odd. The
> queries seem to be converted to lowercase before they ever reach the SQL
> engine.
Correct me if I'm wrong, but doesn't it look like a trend in PostgreSQL
development? Instead of adding options and keeping the standard or
previous behaviour, a new behaviour is attached to old syntax, and if
you want to keep the standard or old results you have to do something else.
The "Right Thing"(TM) to do in this case would be to be case insensitive
by default, according to the traditional (if not standard) SQL practice,
and do case sensitiveness if using quotes.
Just my 2c.
>> Maybe this isn't technically a bug, but I found it strange. With
> PostgreSQL
>> 7.0.3 and 7.1beta6, I can create a database "FOO", but can only later
> connect to
>> it as "foo". I'm not sure if this is a psql thing or a backend thing, or
> if
>> it's intended to be this way, but it makes some of my scripts more
> complicated.
>
>> --
>> Shaw Terwilliger <sterwill@sourcegear.com>
--
_
/ \ Leandro Guimarães Faria Corsetti Dutra +55 (11) 3040 8913
\ / Amdocs at Bell Canada +1 (514) 786 87 47
X Support Center, São Paulo, Brazil mailto:adbaamd@bell.ca
/ \ http://terravista.pt./Enseada/1989/ mailto:leandrod@amdocs.com