From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Marlene Reiterer <marlene(dot)reiterer(dot)03(at)gmail(dot)com>, Wolfgang Walther <walther(at)technowledgy(dot)de> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Docs: Order of json aggregate functions |
Date: | 2024-07-31 08:12:50 |
Message-ID: | 0a2340d8a9126f5a5d276ba0bfd4becee31f017f.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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(at)technowledgy(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Shubham Khanna | 2024-07-31 08:42:01 | Re: Pgoutput not capturing the generated columns |
Previous Message | Kirill Reshke | 2024-07-31 07:31:09 | Re: Lack of possibility to specify CTAS TAM |