| From: | Christian Convey <christian(dot)convey(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Tackling JsonPath support |
| Date: | 2016-09-15 16:05:30 |
| Message-ID: | CAPfS4Zy0RCJstWT3sRhKZO6db+xxZeAL7wmOVG5QUK=P8bXWZQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Sep 5, 2016 at 1:44 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
...
> I wrote XMLTABLE function, and I am thinking about JSON_TABLE function. But
> there is one blocker - missing JsonPath support in our JSON implementation.
>
> So one idea - implement JsonPath support and related JSON query functions.
> This can help with better standard conformance.
Hi Pavel,
Are you still looking for someone to add the JsonPath support to the
JSON implementation? And if so, how urgently are people waiting for
it?
I'd be happy to start working on a patch, but since I'm new to PG
development, I'm probably not the fastest person to get it done.
Kind regards,
Christian
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-09-15 16:06:43 | Re: Surprising behaviour of \set AUTOCOMMIT ON |
| Previous Message | Tomas Vondra | 2016-09-15 16:04:25 | Re: Vacuum: allow usage of more than 1GB of work mem |