I am sure it is a Good Thing, thank you for the explanation. I will just
have to change my thinking to all lowercase and get used to it.
Sort of on the same topic, does anyone know of a PostgreSQL primer for those
making the change from MySQL. Changing religions :} is never easy,
something to ease the transition and point out the differences and gotchas
would be very helpful.
Thanks for the help,
Brian
+++++++++++++++++++++++++++++
Flash web sites from $149/year w/ hosting
http://www.eflashcash.com/er/websuccess/
+++++++++++++++++++++++++++++
> On Thu, 5 Apr 2001, 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.
>
> Everything is postgresql is lowercased, unless system identifiers (double
> quotes) are wrapped around it.
>
> CREATE DATABASE foo
>
> is the same as
>
> CREATE DATABASE FOO
>
> or
>
> CREATE DATABASE Foo
>
>
> You must connect to it with
>
> \c foo
>
>
> However, if you
>
> CREATE TABLE "FOO"
>
> then it is not lowercased. You must connect as
>
> \c FOO
>
>
> I think this is a Good Thing. It allows most people to have
> case-insensitive system identifiers (at least they appear
> case-insensitive, since it lowercases everything). This plays well with
> other database systems. If you want case-sensitive identifiers, you just
> wrap them wiuth the double quotes.
>
> (cf to the mess in MySQL, where some things are case-sensitive, and some
> things aren't, and it varies based on whether the server OS is case
> sensitive. Ick.)
>
> --
> Joel Burton <jburton@scw.org>
> Director of Information Systems, Support Center of Washington
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
