Re: TODO items for window functions
| От | Tom Lane |
|---|---|
| Тема | Re: TODO items for window functions |
| Дата | |
| Msg-id | 26955.1230739481@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: TODO items for window functions (Alvaro Herrera <alvherre@commandprompt.com>) |
| Ответы |
Re: TODO items for window functions
Re: TODO items for window functions |
| Список | pgsql-hackers |
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Heikki Linnakangas escribi�:
>> Tom Lane wrote:
>>> pg_catalog | nth_value | anyelement | anyelement, integer OVER window
>>
>> That looks like "OVER window" is associated with the "integer", like
>> DEFAULT. I don't have any better suggestions, though.
> pg_catalog | nth_value | anyelement | (anyelement, integer) OVER window
Yeah, I had considered that too, and it has a distinct advantage for
parameterless functions like rank():
Schema | Name | Result data type | Argument data types
------------+------+------------------+---------------------pg_catalog | rank | bigint | OVER
windowpg_catalog| rank | bigint | () OVER window
The latter is definitely clearer about what you're supposed to do.
However, it seems kind of inconsistent to do this for window functions
unless we also make \df start putting parens around the argument lists
for regular functions. Comments?
regards, tom lane
В списке pgsql-hackers по дате отправления: