In-Reply-To: <20040928222637.L43334@megazone.bigpanda.com>
References: <DD3C2AD6-11C9-11D9-8537-000D93AE0944@sitening.com>
	<20040928222637.L43334@megazone.bigpanda.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <0E177963-1214-11D9-8537-000D93AE0944@sitening.com>
Content-Transfer-Encoding: 7bit
Cc: pgsql-docs@postgresql.org
From: Thomas F.O'Connell <tfo@sitening.com>
Subject: EXTRACT Clarification
Date: Wed, 29 Sep 2004 08:35:32 -0400
To: Stephan Szabo <sszabo@megazone.bigpanda.com>

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.

-tfo

On Sep 29, 2004, at 1:30 AM, Stephan Szabo wrote:

> sszabo@bigpanda.com
>
> 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 
> SQL
> defined it.