Horton

Re: ON ERROR in json_query and the like

David G. Johnston <david.g.johnston@gmail.com>

View thread View on postgr.es
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Markus Winand <markus.winand@winand.at>
Cc: jian he <jian.universality@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2024-06-12T13:13:52Z
Lists: pgsql-hackers 
On Wednesday, June 12, 2024, Markus Winand <markus.winand@winand.at> wrote:
>
>
> 10.14 SR 1: The declared type of the <value expression> simply contained
> in the <JSON input expression> immediately contained in the <JSON context
> item> shall be a string type or a JSON type.


> It might be best to think of it as two separate functions, overloaded:
>
> JSON_VALUE(context_item JSONB, path_expression …)
> JSON_VALUE(context_item TEXT, path_expression …)


Yes, we need to document that we deviate from (fail to fully implement) the
standard here in that we only provide jsonb parameter functions, not text
ones.

David J.

Commits

  1. SQL/JSON: Document behavior when input document is not jsonb

  2. SQL/JSON: Correctly enforce the default ON EMPTY behavior

  3. Create infrastructure for "soft" error reporting.