From: | Scott Marlowe <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Cc: | Paul M Foster <paulf(at)quillandmouse(dot)com> |
Subject: | Re: Quotes in SQL |
Date: | 2002-05-14 15:19:53 |
Message-ID: | Pine.LNX.4.33.0205140919090.2855-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 14 May 2002, Tom Lane wrote:
> 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 ...
The simple rule of thumb to prevent all this is just use lower case for
everything. It sure makes my life easier.
From | Date | Subject | |
---|---|---|---|
Next Message | Martín Marqués | 2002-05-14 15:23:14 | Re: restoreing dumps fail |
Previous Message | Scott Marlowe | 2002-05-14 15:18:38 | Re: Strange interaction with php's pg_query |