| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Paul M Foster <paulf(at)quillandmouse(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Quotes in SQL |
| Date: | 2002-05-14 04:12:32 |
| Message-ID: | 22835.1021349552@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Paul M Foster <paulf(at)quillandmouse(dot)com> writes:
>> That's normal. If you use quotes when you create the table, you (usually)
>> need quotes when accessing the fields. If you don't use quotes when creating
>> the table, you don't need them when accessing.
> Huh? Doesn't the parser strip off the quotes? Are you saying it stores
> the quotes and expects you to provide them when accessing the fields?
No; the above is just a rule of thumb for staying out of case-folding
trouble, which is what seems to be biting you. See
http://www.ca.postgresql.org/users-lounge/docs/7.2/postgres/sql-syntax.html#SQL-SYNTAX-IDENTIFIERS
and pay particular attention to the footnote ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2002-05-14 04:17:09 | Re: Quotes in SQL |
| Previous Message | Xinlin Qian | 2002-05-14 04:05:04 | ERROR: SET TRANSACTION ISOLATION LEVEL must be called before any query |