| From: | Florents Tselai <florents(dot)tselai(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Add SQL/JSON ON MISMATCH clause to JSON_VALUE |
| Date: | 2026-01-24 17:14:22 |
| Message-ID: | CA+v5N42Kn65HauYbZJ=bAVHjzdp=wCg64dd+WzRmtu=Uu1z+Ow@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello hackers,
Here's a patch that attempts to $subject.
My original motivation was to implement this for JSON_TABLE,
but I realized it would be better to start with a smaller scope
by targeting the basic query functions first.
Currently this v1 passes the tests I've put for JSON_VALUE.
I've had trouble making JSON_QUERY work too,
so I suspect that although my tests pass,
there may be something I'm missing in the executor side of things.
While I troubleshoot that it'd be nice to get some feedback for this
version.
Regards,
Flo
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Add-SQL-JSON-ON-MISMATCH-clause-to-JSON_VALUE.patch | application/octet-stream | 23.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-01-24 17:54:08 | Re: ABI Compliance Checker GSoC Project |
| Previous Message | Andres Freund | 2026-01-24 15:56:21 | Re: unnecessary executor overheads around seqscans |