| From: | Nitin Motiani <nitinmotiani(at)google(dot)com> |
|---|---|
| To: | Narayanan Venkateswaran <narayananvpostgres(at)gmail(dot)com> |
| Cc: | theshallow27(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
| Subject: | Re: BUG #19737: Empty `JSON_OBJECT` cannot use documented `ON NULL` or unique-key clauses |
| Date: | 2026-10-21 08:45:20 |
| Message-ID: | CAH5HC97O5fkwYkyZr-YtzugAniNNJ3YxS=znSw2oCeQqOB0KXQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> > I am working on a follow-up patch that addresses json_array also, I
> > shall submit it soon.
>
> Please find attached the patch that fixes the problem in json_array also.
>
Thanks Narayanan. It seems to work fine. One concern I have is that
this differs from the SQL standard. Since the documentation is already
different, this is probably the right fix to make. But the commit
message and the documentation should reflect this change. What do you
think?
Also can you create a commitfest entry for this?
Regards,
Nitin Motiani
Google
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Staroverov Ilja | 2026-10-21 09:04:09 | Re: pg_stat_statements replaces SQL/JSON ON EMPTY / ON ERROR keywords with parameters |
| Previous Message | Nitin Motiani | 2026-10-21 08:34:57 | Re: BUG #19770: CREATE TABLE (LIKE ...) PARTITION BY copies a NO INHERIT not-null constraint; NULLs then go into par |