Switching this thread to DOCS and renaming it...
Anyway, I think that this situation calls for some clarification in the
docs. If others agree, I'd be happy to submit a potential patch.
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.
Is this wording acceptable? I'd imagine putting it at the end of 9.8.1.
Also, are there other expressions that fall into this category? I don't
know the spec well enough to know.
On Sep 29, 2004, at 1:30 AM, Stephan Szabo wrote:
> On Tue, 28 Sep 2004, Thomas F.O'Connell wrote:
>> From 11.5 in the docs:
>> "The syntax of the CREATE INDEX command normally requires writing
>> parentheses around index expressions, as shown in the second example.
>> The parentheses may be omitted when the expression is just a function
>> call, as in the first example."
>> But when I try this:
>> db=# CREATE INDEX expression_idx on some_table( extract( year from
>> some_column ) );
> Extract(year from some_column) is not really just a function call it's
> an expression that looks similar to a function call because that's how
> defined it.
In response to
pgsql-docs by date
|Next:||From: Kris Jurka||Date: 2004-09-29 13:21:49|
|Subject: Add tablespace index entry|
|Previous:||From: Stephan Szabo||Date: 2004-09-29 05:30:55|
|Subject: Re: Indexes on Expressions -- Parentheses|
pgsql-general by date
|Next:||From: Kris Jurka||Date: 2004-09-29 13:25:59|
|Subject: Re: EXTRACT Clarification|
|Previous:||From: Najib Abi Fadel||Date: 2004-09-29 12:29:25|
|Subject: Re: Multiple Rules :: Postgres Is confused !!|