From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Erik Wienhold <ewie(at)ewie(dot)name> |
Subject: | Re: ❓ JSON Path Dot Precedence |
Date: | 2024-07-08 16:17:09 |
Message-ID: | CAKFQuwZypRzFbv8MZ62dOo2Xs=mZ9HB5sMi02K46Mcq0vWSbtQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jul 8, 2024 at 9:12 AM David E. Wheeler <david(at)justatheory(dot)com>
wrote:
> On Jul 8, 2024, at 12:05, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
> wrote:
>
> > Does the standard even have a separate type here or is that our
> implementation detail invention?
>
> Sorry, separate type for what?
>
>
We created a data type named: jsonpath. Does the standard actually have
that data type and defined parsing behavior or does it just have functions
where one of the inputs is text whose contents are a path expression?
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Paul Jungwirth | 2024-07-08 16:32:55 | Re: Add GiST support for mixed-width integer operators |
Previous Message | David E. Wheeler | 2024-07-08 16:11:58 | Re: ❓ JSON Path Dot Precedence |