Re: Jsonpath ** vs lax mode - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Jsonpath ** vs lax mode
Date
Msg-id 20210121133510.GA8139@alvherre.pgsql
Whole thread Raw
In response to Re: Jsonpath ** vs lax mode  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: Jsonpath ** vs lax mode  (Alexander Korotkov <aekorotkov@gmail.com>)
List 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



pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Identify missing publications from publisher while create/alter subscription.
Next
From: Pavel Stehule
Date:
Subject: Re: patch: reduce overhead of execution of CALL statement in no atomic mode from PL/pgSQL