From: | Tim Hart <tjhart(at)mac(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org, Chris <dmagick(at)gmail(dot)com> |
Subject: | Re: Question about the enum type |
Date: | 2008-02-18 06:26:07 |
Message-ID: | 70326e4da0629ad3f8841234ceff7fb0@mac.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Feb 18, 2008, at 12:10 AM, Tom Lane wrote:
>> Would it have been reasonable to expect some kind of notice or warning
>> message stating that 'position' was special, and
>> <double-quote>position<double-quote> would be used instead?
>
> The way you phrase that makes me think you misunderstand what's
> happening here. The name of the type isn't "position" with double
> quotes, it's just position. You have to double-quote it when you
> use it to prevent the parser from thinking that the special SQL
> POSITION function call syntax is coming up. There are other ways
> to do that though, for example if you write public.position (or
> whatever
> schema it's in) then you won't need double quotes.
I did misunderstand. I understand now that the quotes are used to call
out the string literally, and to avoid syntax-related parsing. Thanks
for the help.
Tim
From | Date | Subject | |
---|---|---|---|
Next Message | Mikko Partio | 2008-02-18 07:15:01 | SPI-functions and transaction control |
Previous Message | Oleg Bartunov | 2008-02-18 06:25:14 | Re: DB design: How to store object properties? |