From: | Christian Convey <christian(dot)convey(at)gmail(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Tackling JsonPath support |
Date: | 2016-11-28 17:29:31 |
Message-ID: | CAPfS4ZwDb5-7rzK-cDewbBZ=2n-W+bdOGiwAPF9U9io8ihUmFw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Nov 28, 2016 at 5:20 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
wrote:
...
> Con: "JSON path expression" is a recurring them in the *grammars* of
>> user-facing operators in [1], [2], [3], and [4]. But it doesn't
>> necessarily follow that the function implemented in Step 2 will provide
>> useful infrastructure for PG's eventual implementations of "JSON_TABLE",
>> etc.
>>
>
> We can implement subset only - our XPath based on libxml2 does it too. The
> good target is support of usual examples on the net.
>
Hi Pavel,
Can you clarify what you meant? I *think* you're saying:
* It's not important for me to match the syntax/semantics of the json-path
implementations found in MySQL / Oracle / DB2 / MS SQL Server, and
* Instead, I should just use examples / explanations on the web as my
guidance.
Thanks,
Christian
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-11-28 17:31:13 | Re: UNDO and in-place update |
Previous Message | Alvaro Herrera | 2016-11-28 17:28:40 | Re: pg_dump / copy bugs with "big lines" ? |