Improve docs about using ORDER BY to control aggregate input order. David Johnston pointed out that the original text here had been obsoleted by SQL:2008, which allowed ORDER BY in subqueries. We could weaken the text to describe ORDER-BY-in-subqueries as an optional SQL feature that's possibly unportable; but then the exact same statements would apply to the alternative it's being compared to (ORDER-BY-in-aggregate-calls). So really that would be pretty useless; let's just take out the sentence entirely. Instead, point out the hazard that any extra processing in the upper query might cause the subquery output order to be destroyed.
Discussion: <CAKFQuwbAX=io9qbpn7_jr+bnuwm9fyx8wbepuvg0p+nzhp6...@mail.gmail.com> Branch ------ master Details ------- http://git.postgresql.org/pg/commitdiff/82eafabeaaf12231a85ed67bbf4eae698aacb1c9 Modified Files -------------- doc/src/sgml/func.sgml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
