Re: jsonpath

2018-01-07 21:20 GMT+01:00 Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>:

>
>
> On 01/07/2018 03:16 PM, Pavel Stehule wrote:
> >
> >
> > 2018-01-07 21:14 GMT+01:00 Andrew Dunstan
> > <andrew(dot)dunstan(at)2ndquadrant(dot)com <mailto: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>
> > <mailto: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
> >
> >
>
>
> OK. You can help by also reviewing and testing the small patch at
> </message-id/f16a6408-45fe-b299-
> 02b0-41e50a1c3023%402ndQuadrant.com>
>

I'll look there

Regards

Pavel

> thanks
>
> cheers
>
> andrew
>
> --
> Andrew Dunstan https://www.2ndQuadrant.com
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
>