public inbox for [email protected]  

help / color / mirror / Atom feed

From: Nikita Malakhov <[email protected]>
To: Amit Langote <[email protected]>
Cc: pgsql-hackers <[email protected]>
Subject: Re: SQL/JSON json_table plan clause
Date: Tue, 4 Feb 2025 14:50:35 +0300
Message-ID: <CAN-LCVNSSCTdMjSFHKMkPUDcxNiGX1qn=EWMmmph8dmhkOaj_g@mail.gmail.com> (raw)
In-Reply-To: <CA+HiwqGqz1+jvrWHHzYSnzuVZPp4v-vfEyX-hB=3hTP3Asf78Q@mail.gmail.com>
References: <CAN-LCVP7HXmGu-WcinsHvdKqMGEdv=1Y67H4U58F6Y=Q0M5GyQ@mail.gmail.com>
	<CA+HiwqGqz1+jvrWHHzYSnzuVZPp4v-vfEyX-hB=3hTP3Asf78Q@mail.gmail.com>

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 <[email protected]> wrote:

> Hi Nikita,
>
> On Wed, Dec 18, 2024 at 12:11 AM Nikita Malakhov <[email protected]>
> 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/

view thread (9+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: SQL/JSON json_table plan clause
  In-Reply-To: <CAN-LCVNSSCTdMjSFHKMkPUDcxNiGX1qn=EWMmmph8dmhkOaj_g@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox