Re: ❓ JSON Path Dot Precedence

From: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ❓ JSON Path Dot Precedence
Date: 2024-04-10 20:44:51
Message-ID: 762BE227-F066-43F2-A61D-DBFB7844CE65@justatheory.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Apr 10, 2024, at 10:29, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:

> So the whole thing is
>
> <JSON path literal> <period> <JSON path key name>
>
> The syntax of <JSON path literal> and <JSON path key name> is then punted to ECMAScript 5.1.
>
> 0x2 is a HexIntegerLiteral. (There can be no dots in that.)
>
> p10 is an Identifier.
>
> So I think this is all correct.

That makes sense, thanks. It’s just a little odd to me that the resulting path isn’t a query at all. To Erik’s point: what path can `'0x2.p10` even select?

Best,

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Melanie Plageman 2024-04-10 20:50:44 Re: Table AM Interface Enhancements
Previous Message Tom Lane 2024-04-10 20:40:05 Re: Issue with the PRNG used by Postgres