Re: SQL:2023 JSON simplified accessor support

From: Alexandra Wang <alexandra(dot)wang(dot)oss(at)gmail(dot)com>
To: Matheus Alcantara <matheusssilv97(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Nikita Glukhov <glukhov(dot)n(dot)a(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, "David E(dot) Wheeler" <david(at)justatheory(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com>
Subject: Re: SQL:2023 JSON simplified accessor support
Date: 2025-03-03 20:22:49
Message-ID: CAK98qZ14uKKRVFg4ibzMfReYaZD6Byxq8nYnvNNtXNjCfcd8kQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Matheus,

On Mon, Mar 3, 2025 at 1:43 PM Matheus Alcantara <matheusssilv97(at)gmail(dot)com>
wrote:

> On Mon, Mar 3, 2025 at 4:16 PM Matheus Alcantara
> <matheusssilv97(at)gmail(dot)com> wrote:
> >
> > Hi Alex,
> >
> > The code comments and the commit messages help a lot when reviewing!
> Thanks for
> > the new version.
> >
> > The code LGTM and check-world is happy. I've also performed some tests
> and
> > everything looks good!

> Just some minor points about this new version:
> >
> > ## v9-0005
> >
> > Typo on commit message title

> ## v9-0006
> >
> > > + * The following functions create various types of JsonPathParseItem
> nodes,
> > > + * which are used to build JsonPath expressions for jsonb simplified
> accessor.
> > >
> > Just to avoid misinterpretation I think that we can replace "The
> following
> > functions" with "The make_jsonpath_item_* functions" since we can have
> more
> > functions in the future that are not fully related with these. Does that
> make
> > sense?
>

Thank you so much for reviewing! I've attached v10, which addresses your
feedback.

On Mon, Mar 3, 2025 at 1:43 PM Matheus Alcantara <matheusssilv97(at)gmail(dot)com>
wrote:

> Sorry, I've forgotten to include a question. Do you have anything in mind
> about
> documentation changes for this patch?
>

For the documentation, I’m thinking of adding it under JSON Types [1].
I’d either add a new “Simple Dot-Notation” section after jsonb
subscripting [2] or replace it. Let me know what you think.

[1] https://www.postgresql.org/docs/current/datatype-json.html#DATATYPE-JSON
[2]
https://www.postgresql.org/docs/current/datatype-json.html#JSONB-SUBSCRIPTING

Best,
Alex

Attachment Content-Type Size
v10-0004-Extract-coerce_jsonpath_subscript.patch application/octet-stream 5.5 KB
v10-0002-Allow-Generic-Type-Subscripting-to-Accept-Dot-No.patch application/octet-stream 10.3 KB
v10-0003-Export-jsonPathFromParseResult.patch application/octet-stream 2.5 KB
v10-0005-Enable-String-node-as-field-accessors-in-generic.patch application/octet-stream 7.7 KB
v10-0001-Allow-transformation-of-only-a-sublist-of-subscr.patch application/octet-stream 8.8 KB
v10-0006-Implement-read-only-dot-notation-for-jsonb.patch application/octet-stream 26.8 KB
v10-0007-Allow-wild-card-member-access-for-jsonb.patch application/octet-stream 18.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2025-03-03 20:31:42 Re: scalability bottlenecks with (many) partitions (and more)
Previous Message Tom Lane 2025-03-03 20:00:43 Re: Ubsan complaint on kestrel