Hi Amit! No, JSON_TABLE is ok. I've meant that in the previous approach to PLAN clause implementation there were some wrong tests.
On Tue, Feb 4, 2025 at 6:05 AM Amit Langote <amitlangot...@gmail.com> wrote: > Hi Nikita, > > On Wed, Dec 18, 2024 at 12:11 AM Nikita Malakhov <huku...@gmail.com> > wrote: > > > > 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. > > Thanks for working on this. > > > 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. > > Sorry, I don't fully understand this paragraph. Do you mean that > there might be bugs in the existing JSON_TABLE() functionality that > was committed into v17? > > -- > Thanks, Amit Langote > -- Regards, Nikita Malakhov Postgres Professional The Russian Postgres Company https://postgrespro.ru/
