Re: FILTER for aggregates [was Re: Department of Redundancy Department: makeNode(FuncCall) division]
От | Andrew Gierth |
---|---|
Тема | Re: FILTER for aggregates [was Re: Department of Redundancy Department: makeNode(FuncCall) division] |
Дата | |
Msg-id | 7c73f7b5630eb0e2581cbd02696b61b2@news-out.riddles.org.uk обсуждение исходный текст |
Ответ на | Re: FILTER for aggregates [was Re: Department of Redundancy Department: makeNode(FuncCall) division] (David Fetter <david@fetter.org>) |
Ответы |
Re: FILTER for aggregates [was Re: Department of Redundancy
Department: makeNode(FuncCall) division]
Re: FILTER for aggregates [was Re: Department of Redundancy Department: makeNode(FuncCall) division] Re: FILTER for aggregates [was Re: Department of Redundancy Department: makeNode(FuncCall) division] |
Список | pgsql-hackers |
Tom Lane said: > Agreed, separating out the function-call-with-trailing-declaration > syntaxes so they aren't considered in FROM and index_elem seems like > the best compromise. > > If we do that for window function OVER clauses as well, can we make > OVER less reserved? Yes. At least, I tried it with both OVER and FILTER unreserved and there were no grammar conflicts (and I didn't have to do anything fancy to avoid them), and it passed regression with the exception of the changed error message for window functions in the from-clause. So is this the final decision on how to proceed? It seems good to me, and I can work with David to get it done. -- Andrew (irc:RhodiumToad)
В списке pgsql-hackers по дате отправления: