From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Joe Abbate <jma(at)freedomcircle(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Reserved words and delimited identifiers |
Date: | 2011-11-30 03:09:07 |
Message-ID: | CA+Tgmob7gaErynZxMMy4sfs-ffN-tCzy_j=4HWYZJ1d2tLOJkQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Nov 29, 2011 at 7:29 PM, Joe Abbate <jma(at)freedomcircle(dot)com> wrote:
> It seems to me that since a TYPE in a column definition or function
> argument can be a non-native TYPE, it could be a reserved word and
> therefore it should always be allowable to quote the TYPE. Can someone
> please explain why that is not the case?
Type names as they appear in pg_type.typname can always be quoted.
But some types, like int4, have alternate names - e.g. int4 can be
specified as integer or int, and foat8 can be specified using the
two-word phrase double precision. These alternate names are keywords
when unquoted, but identifiers (with a different meaning) when quoted.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-11-30 03:12:13 | Re: DOMAINs and CASTs |
Previous Message | Robert Haas | 2011-11-30 03:02:50 | Re: Patch - Debug builds without optimization |