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:40:11
Message-ID: 666B9F7B.4030302@acm.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06/13/24 21:24, David G. Johnston wrote:
> I'm content that the operators in the 'filter operators' table need to be
> within filter but then I cannot reconcile why this example worked:
>
> 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>.

Regards,
-Chap

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2024-06-14 01:46:15 Re: jsonpath: Missing Binary Execution Path?
Previous Message David G. Johnston 2024-06-14 01:24:23 Re: jsonpath: Missing Binary Execution Path?