From: | Paul M Foster <paulf(at)quillandmouse(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Quotes in SQL |
Date: | 2002-05-14 03:51:48 |
Message-ID: | 20020513235148.A22819@quillandmouse.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, May 14, 2002 at 11:31:03AM +1000, Martijn van Oosterhout wrote:
> On Mon, May 13, 2002 at 02:49:47PM -0600, Randall Barber wrote:
> > Hi--I'm completely new to PostGres... From what I read in the
> documentation, sql here is same as there.
> >
> > SELECT * FROM FOO.BAR WHERE FOO.BAR.BAZ='1234';
> >
> > However, I just finished building my own PostGres and when I try to use
> it, I have to do stuff like this:
> >
> > SELECT * FROM "FOO"."BAR" WHERE "FOO"."BAR"."BAZ" = '1234';
> >
> > Is this a Postgres thing? Or did I compile it wrong? Or is it an option
> to create_db?
>
> 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?
(Pardon if this seems like an incredibly dumb question.)
Paul
From | Date | Subject | |
---|---|---|---|
Next Message | Xinlin Qian | 2002-05-14 04:05:04 | ERROR: SET TRANSACTION ISOLATION LEVEL must be called before any query |
Previous Message | Tom Lane | 2002-05-14 03:31:51 | Re: Strange interaction with php's pg_query |