From: | Jeff Eckermann <jeff_eckermann(at)yahoo(dot)com> |
---|---|
To: | Paul Makepeace <postgresql(dot)org(at)paulm(dot)com>, PostgreSQL Novice <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: [bug?] oddity creating table with uppercase initial |
Date: | 2003-06-08 18:41:51 |
Message-ID: | 20030608184151.27602.qmail@web20807.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
SQL is case insensitive, except for the actual data.
Most commercial databases deal with this by forcing
everything to upper case (the SQL standard appears to
support this approach); PostgreSQL forces everything
to lower case. This was a choice made long ago, and
nobody is in a hurry to change it. Either way, you
will have a problem.
The answer is to double quote your mixed case
identifiers: select * from "Banks";
The name must have been quoted when the table was
created; if you are unaware of that, you must have
used some administration/migration tool that quoted
the names without your knowing.
Since you must remember to quote the names every time
you use them, mixed case names are a trap waiting to
spring. My experience is that they are more trouble
than they are worth.
__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | A.Bhuvaneswaran | 2003-06-09 04:04:17 | Re: FATAL 1 |
Previous Message | Bruno Wolff III | 2003-06-08 14:15:50 | Re: [bug?] oddity creating table with uppercase initial |