Re: remaining sql/json patches - Mailing list pgsql-hackers

From Amit Langote
Subject Re: remaining sql/json patches
Date
Msg-id CA+HiwqHx0kAe74hXY-M3GVqZAmZWx+GuAksjcG4iK-ZHoaeBLg@mail.gmail.com
Whole thread Raw
In response to Re: remaining sql/json patches  (Amit Langote <amitlangote09@gmail.com>)
Responses Re: remaining sql/json patches
Re: remaining sql/json patches
List pgsql-hackers
On Wed, Mar 27, 2024 at 1:34 PM Amit Langote <amitlangote09@gmail.com> wrote:
> On Wed, Mar 27, 2024 at 12:42 PM jian he <jian.universality@gmail.com> wrote:
> > hi.
> > I don't fully understand all the code in json_table patch.
> > maybe we can split it into several patches,
>
> I'm working on exactly that atm.
>
> > like:
> > * no nested json_table_column.
> > * nested json_table_column, with PLAN DEFAULT
> > * nested json_table_column, with PLAN ( json_table_plan )
>
> Yes, I think it will end up something like this.  I'll try to post the
> breakdown tomorrow.

Here's patch 1 for the time being that implements barebones
JSON_TABLE(), that is, without NESTED paths/columns and PLAN clause.
I've tried to shape the interfaces so that those features can be added
in future commits without significant rewrite of the code that
implements barebones JSON_TABLE() functionality.  I'll know whether
that's really the case when I rebase the full patch over it.

I'm still reading and polishing it and would be happy to get feedback
and testing.

--
Thanks, Amit Langote

Attachment

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: BitmapHeapScan streaming read user and prelim refactoring
Next
From: Jeff Davis
Date:
Subject: Re: Change GUC hashtable to use simplehash?