As always, the solution is in the postgresql documentation. Using exists()
from a filter prior to accessing an optional field solves my problem. I can
have both strict mode and access to optional fields without getting an
error this way.
On Fri, Oct 15, 2021 at 6:50 PM Seref Arikan wrote:
>
I have json data which is based on arbitrary levels of hierarchy. The json
objects I need to query are at an unknown depth in the document, which
means I have to use the recursive wildcard member accessor (.**)
The problem is, the path to these unknown depths also contain arrays, and
when .** acce
