Re: Docs: Order of json aggregate functions
Laurenz Albe <laurenz.albe@cybertec.at>
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Marlene Reiterer <marlene.reiterer.03@gmail.com>, Wolfgang Walther <walther@technowledgy.de>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-07-31T08:12:50Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Doc: alphabetize aggregate function table
- 4f601b9598a4 16.5 landed
- 2645f6d643d9 17.0 landed
- 5bb9ba273989 18.0 landed
On Tue, 2024-07-23 at 11:45 +0200, Marlene Reiterer wrote: > Am Mo., 22. Juli 2024 um 15:19 Uhr schrieb Wolfgang Walther <walther@technowledgy.de>: > > > > The order of json related aggregate functions in the docs is currently > > like this: > > > > [...] > > json_agg > > json_objectagg > > json_object_agg > > json_object_agg_strict > > json_object_agg_unique > > json_arrayagg > > json_object_agg_unique_strict > > max > > min > > range_agg > > range_intersect_agg > > json_agg_strict > > [...] > > > > json_arrayagg and json_agg_strict are out of place. > > > > Attached patch puts them in the right spot. This is the same down to v16. > > I compiled and it worked and didn't throw an error. > > The changes to the patch seem useful in my perspective, for making it > easier to find the functions in the documentation, so people will find > them easier. > > There is another table which isn't sorted too, the "Hypothetical-Set > Aggregate Functions". Which would be in need of an alphabetical > sorting too, if all the tables on this side > of the documentation should look alike. There are only four hypothetical-set aggregate functions, so it is no problem to find a function in that list. I would say that it makes sense to apply the proposed patch, even if we don't sort that short list. Yours, Laurenz Albe