Re: ON ERROR in json_query and the like - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: ON ERROR in json_query and the like
Date
Msg-id CAKFQuwa8UxPDD-E78C6knatVFoqfxxNPBcLfj2445eNohmvK9g@mail.gmail.com
Whole thread Raw
In response to Re: ON ERROR in json_query and the like  (Markus Winand <markus.winand@winand.at>)
Responses Re: ON ERROR in json_query and the like
List pgsql-hackers
On Thursday, June 20, 2024, Markus Winand <markus.winand@winand.at> wrote:


> On 21.06.2024, at 06:46, David G. Johnston <david.g.johnston@gmail.com> wrote:
>>

>
> 2 also has the benefit of being standard conforming while 1 does not.

Why do you think so? Do you have any references or is this just based on previous statements in this discussion?


Hearsay.


> 4) If ALREADY PARSED is False, then it is implementation-defined whether the
> following rules are applied:
> a) The General Rules of Subclause 9.36, "Parsing JSON text", are applied with
> JT as JSON TEXT, an implementation-defined <JSON key uniqueness constraint>
> as UNIQUENESS CONSTRAINT, and FO as FORMAT OPTION; let ST be the STATUS and
> let CISJI be the SQL/JSON ITEM returned from the application of those
> General Rules.
> b) If ST is not successful completion, then ST is returned as the STATUS of
> this application of these General Rules, and no further General Rules of
> this Subclause are applied.

But maybe I’m mis-interpreting that snippet and Nikita’s related commentary regarding have chosen between options for this implementation-defined feature.

David j.

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Allow non-superuser to cancel superuser tasks.
Next
From: Peter Eisentraut
Date:
Subject: Re: jsonapi type fixups