Horton

Re: SQL/JSON revisited

Amit Langote <amitlangote09@gmail.com>

View thread View on postgr.es
From: Amit Langote <amitlangote09@gmail.com>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Andrew Dunstan <andrew@dunslane.net>, Andres Freund <andres@anarazel.de>, vignesh C <vignesh21@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>, e.indrupskaya@postgrespro.ru
Date: 2023-03-15T12:49:49Z
Lists: pgsql-hackers

Attachments

Hi,

On Thu, Mar 9, 2023 at 10:08 PM Peter Eisentraut
<peter.eisentraut@enterprisedb.com> wrote:
> On 08.03.23 22:40, Andrew Dunstan wrote:
> > These both seem like things not worth holding up progress for, and I
> > think it would be good to get these patches committed as soon as
> > possible. My intention is to commit them (after some grammar
> > adjustments) plus their documentation in the next few days.
>
> If possible, the documentation for each incremental part should be part
> of that patch, not a separate all-in-one patch.

Here's a version that includes documentation of the individual bits in
their own commits.  I've also merged the patch to add the PLAN clause
to JSON_TABLE into the patch that adds JSON_TABLE itself.

-- 
Thanks, Amit Langote
EDB: http://www.enterprisedb.com

Commits

  1. Add SQL/JSON query functions

  2. Add soft error handling to some expression nodes

  3. Adjust populate_record_field() to handle errors softly

  4. Refactor code used by jsonpath executor to fetch variables

  5. Code review for recent SQL/JSON commits

  6. Fix inconsistencies and style issues in new SQL/JSON code

  7. Don't install postmaster symlink anymore

  8. Revert SQL/JSON features

  9. Doc: standardize markup a bit more.