| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Markus Winand <markus(dot)winand(at)winand(dot)at> |
| Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ON ERROR in json_query and the like |
| Date: | 2024-06-12 13:13:52 |
| Message-ID: | CAKFQuwb50BAaj83Np+1O6xe3_T6DO8w2mxtFbgSbbUng+abrqA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wednesday, June 12, 2024, Markus Winand <markus(dot)winand(at)winand(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Winand | 2024-06-12 13:22:15 | Re: ON ERROR in json_query and the like |
| Previous Message | Justin Pryzby | 2024-06-12 13:10:23 | Re: CI and test improvements |