From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Oleg Bartunov <obartunov(at)gmail(dot)com>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru> |
Subject: | Re: jsonpath |
Date: | 2018-01-07 20:16:05 |
Message-ID: | CAFj8pRBCvhgLCROfSCPGmwWZpSY+dKQN4O9xRe+1-wjBiXiHkA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2018-01-07 21:14 GMT+01:00 Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>:
>
>
> On 01/07/2018 03:00 PM, Pavel Stehule wrote:
> >
> >
> > 2018-01-07 20:31 GMT+01:00 Andrew Dunstan
> > <andrew(dot)dunstan(at)2ndquadrant(dot)com <mailto:andrew(dot)dunstan(at)2ndquadrant(dot)com
> >>:
> >
> >
> > Next up in the proposed SQL/JSON feature set I will review the three
> > jsonpath patches. These are attached, extracted from the patch set
> > Nikita posted on Jan 2nd.
> >
> >
> > Note that they depend on the TZH/TZM patch (see separate email
> > thread).
> > I'd like to be able to commit that patch pretty soon.
> >
> >
> > I did few tests - and it is working very well.
> >
> >
>
>
> You mean on the revised TZH/TZM patch that I posted?
>
no - I tested jsonpath implementation
Pavel
>
> cheers
>
> andrew
>
> --
> Andrew Dunstan https://www.2ndQuadrant.com
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2018-01-07 20:20:13 | Re: jsonpath |
Previous Message | Andrew Dunstan | 2018-01-07 20:14:41 | Re: jsonpath |