| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Thomas F(dot)O'Connell" <tfo(at)sitening(dot)com>, pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: EXTRACT Clarification |
| Date: | 2004-09-29 15:40:10 |
| Message-ID: | 20040929083745.L61021@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-general |
On Wed, 29 Sep 2004, Tom Lane wrote:
> "Thomas F.O'Connell" <tfo(at)sitening(dot)com> writes:
> > I'm thinking something like this (with thanks to Stephan):
>
> > Note: EXTRACT is not a true function. SQL defines it as an expression
> > that happens to look similar to a function call.
>
> Rather than documenting this, maybe we should change the grammar to
> allow it?
That would work, but presumably then we should be doing all the function
looking things, so probably CAST, EXTRACT, OVERLAY, POSITION, SUBSTRING,
TREAT, TRIM, CONVERT (and any, if any, that weren't in the section of the
grammar I saw those).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas F.O'Connell | 2004-09-29 15:42:26 | Re: EXTRACT Clarification |
| Previous Message | Tom Lane | 2004-09-29 15:32:24 | Re: EXTRACT Clarification |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-09-29 15:40:30 | Re: Setting search paths inside a function (plpgsql) |
| Previous Message | Jonathan Villa | 2004-09-29 15:35:43 | Converting to Java date example |