| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, Oleg Bartunov <obartunov(at)postgrespro(dot)ru>, Teodor Sigaev <teodor(at)postgrespro(dot)ru>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Jsonpath ** vs lax mode |
| Date: | 2021-01-21 13:35:10 |
| Message-ID: | 20210121133510.GA8139@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2021-Jan-21, Alexander Korotkov wrote:
> Requiring strict mode for ** is a solution, but probably too restrictive...
>
> What do you think about making just subsequent accessor after ** not
> to unwrap arrays. That would be a bit tricky to implement, but
> probably that would better satisfy the user needs.
Hmm, why is it too restrictive? If the user needs to further drill into
the JSON, can't they chain json_path_query calls, specifying (or
defaulting to) lax mode for the part doesn't include the ** expression?
--
Álvaro Herrera Valdivia, Chile
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2021-01-21 13:37:39 | Re: patch: reduce overhead of execution of CALL statement in no atomic mode from PL/pgSQL |
| Previous Message | vignesh C | 2021-01-21 13:25:37 | Identify missing publications from publisher while create/alter subscription. |