From: | Erik Rijkers <er(at)xs4all(dot)nl> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Amit Langote <amitlangote09(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, vignesh C <vignesh21(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, e(dot)indrupskaya(at)postgrespro(dot)ru |
Subject: | Re: SQL/JSON revisited |
Date: | 2023-03-29 12:49:40 |
Message-ID: | 4bd6d66f-f89a-6667-008e-323121aa84eb@xs4all.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Op 3/29/23 om 12:27 schreef Alvaro Herrera:
> On 2023-Mar-28, Erik Rijkers wrote:
>
>> In the json_arrayagg() description, it says:
>> 'If ABSENT ON NULL is specified, any NULL values are omitted.'
>> That's true, but as omitting NULL values is the default (i.e., also without
>> that clause) maybe it's better to say:
>> 'Any NULL values are omitted unless NULL ON NULL is specified'
>
> Doh, somehow I misread your report and modified the json_object()
> documentation instead after experimenting with it (so now the
> ABSENT/NULL ON NULL clause is inconsistenly described everywhere).
> Would you mind submitting a patch fixing this mistake?
I think the json_object text was OK. Attached are some changes where
they were needed IMHO.
Erik
>
> ... and pushed it now, after some more meddling.
>
> I'll rebase the rest of the series now.
>
Attachment | Content-Type | Size |
---|---|---|
func.sgml.20230329.diff | text/x-patch | 2.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Drouvot, Bertrand | 2023-03-29 12:51:27 | Re: Autogenerate some wait events code and documentation |
Previous Message | Matthias van de Meent | 2023-03-29 12:49:18 | Re: BufmgrCommit no-op since 2008, remaining uses? |