From: | Nikita Malakhov <hukutoc(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | SQL/JSON json_table plan clause |
Date: | 2024-12-17 15:11:02 |
Message-ID: | CAN-LCVP7HXmGu-WcinsHvdKqMGEdv=1Y67H4U58F6Y=Q0M5GyQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi hackers!
This thread is further work continued in [1], where Amit Langote
suggested starting discussion on the remaining SQL/JSON feature
'PLAN clause for JSON_TABLE' anew.
We'd like to help with merging SQL/JSON patches into vanilla,
and have adapted PLAN clause to recent changes in JSON_TABLE
function.
While doing this we've found that some tests with the PLAN clause
were incorrect, along with JSON_TABLE behavior with this clause.
We've corrected this behavior, but these corrections required reverting
some removed and heavily refactored code, so we'd be glad for review
and feedback on this patch.
Also, we've noticed that Oracle set the PLAN clause for JSON_TABLE
aside for some reason.
--
Regards,
Nikita Malakhov
Postgres Professional
The Russian Postgres Company
https://postgrespro.ru/
Attachment | Content-Type | Size |
---|---|---|
v18-0001-JSON-TABLE-PLAN-clause.patch | application/octet-stream | 124.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Karlsson | 2024-12-17 15:25:22 | Re: fixing tsearch locale support |
Previous Message | AbdelAziz Sharaf | 2024-12-17 15:09:06 | Re: [Feature Request] Schema Aliases and Versioned Schemas |