Re: Variadic aggregates vs. project policy

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Variadic aggregates vs. project policy
Дата
Msg-id 6214.1377871981@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Variadic aggregates vs. project policy  (David Johnston <polobo@yahoo.com>)
Список pgsql-hackers
David Johnston <polobo@yahoo.com> writes:
>>> If we alter syntax for mitigation purposes I'd want to consider requiring
>>> parentheses around the columns that belong to the ORDER BY instead of
>>> using the full extended syntax of WITHIN GROUP.

Unfortunately, that ORDER BY syntax is specified by the SQL standard,
and they didn't say anything about parentheses.  We don't get to
require parens there.

The particular case that's standardized is only array_agg():
   <array aggregate function> ::=     ARRAY_AGG     <left paren> <value expression> [ ORDER BY <sort specification
list>]     <right paren>
 

but, as we customarily do, we didn't restrict the feature to be used only
with that aggregate.
        regards, tom lane



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Pavel Stehule
Дата:
Сообщение: Re: Variadic aggregates vs. project policy
Следующее
От: Stephen Frost
Дата:
Сообщение: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])