From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Scott Bailey <artacus(at)comcast(dot)net> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Naming functions with reserved words |
Date: | 2009-06-17 15:00:07 |
Message-ID: | 26649.1245250807@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Scott Bailey <artacus(at)comcast(dot)net> writes:
> I noticed in the temporal project they used reserved words for their
> functions (union, intersect, etc)
Uh, what project is that exactly, and was it even working within
Postgres?
> But when I try to create a function like that I get an error and I have
> to quote it both when creating the function and when calling it. The
> only difference I can see is they their functions are written in C and
> mine are in SQL. But that doesn't make sense why you could do it in one
> language and not in another.
You can't do it in any language in Postgres. UNION and INTERSECT are
fully reserved keywords, and there just isn't any sane way to avoid
making them so given the restrictions of a LALR(1) parser.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-06-17 15:19:32 | Re: how to cancel a query in progress |
Previous Message | David Fetter | 2009-06-17 14:58:27 | Re: Custom Fields Database Architecture |