Re: jsonpath: Missing Binary Execution Path?

From: Chapman Flack <jcflack(at)acm(dot)org>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: "David E(dot) Wheeler" <david(at)justatheory(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: jsonpath: Missing Binary Execution Path?
Date: 2024-06-14 01:58:57
Message-ID: 666BA3E1.6010308@acm.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06/13/24 21:46, David G. Johnston wrote:
>>> david=# select jsonb_path_query('1', '$ >= 1');
>>
>> Good point. I can't either. No way I can see to parse that as
>> a <JSON path wff>.
>
> Whether we note it as non-standard or not is an open question then, but it
> does work and opens up a documentation question.

Does the fact that it does work raise any potential concern that our
grammar is nonconformant in some way that could present a headache
somewhere else, or down the road with a later standard edition?

Regards,
-Chap

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2024-06-14 02:14:36 Re: jsonpath: Missing Binary Execution Path?
Previous Message Chapman Flack 2024-06-14 01:55:04 Re: Shouldn't jsonpath .string() Unwrap?