Re: SQL/JSON path issues/questions - Mailing list pgsql-hackers

From Thom Brown
Subject Re: SQL/JSON path issues/questions
Date
Msg-id CAA-aLv4Tggy6Z3kaG9n+3SHwOVGN2Yj_MJXfdfwjH_jBNZzJNA@mail.gmail.com
Whole thread Raw
In response to Re: SQL/JSON path issues/questions  (Alexander Korotkov <a.korotkov@postgrespro.ru>)
Responses Re: SQL/JSON path issues/questions
List pgsql-hackers
On Wed, 10 Jul 2019 at 05:58, Alexander Korotkov
<a.korotkov@postgrespro.ru> wrote:
>
> On Mon, Jul 8, 2019 at 12:30 AM Alexander Korotkov
> <a.korotkov@postgrespro.ru> wrote:
> > On Thu, Jul 4, 2019 at 4:38 PM Liudmila Mantrova
> > <l.mantrova@postgrespro.ru> wrote:
> > > Thank  you!
> > >
> > > I think we can make this sentence even shorter, the fix is attached:
> > >
> > > "To refer to a JSON element stored at a lower nesting level, add one or
> > > more accessor operators after <literal>@</literal>."
> >
> > Thanks, looks good to me.  Attached revision of patch contains commit
> > message.  I'm going to commit this on no objections.
>
> So, pushed!

I've just noticed the >= operator shows up as just > in the "jsonpath
Filter Expression Elements" table, and the <= example only shows <.

Thom



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: let's make the list of reportable GUCs configurable (was Re: Add%r substitution for psql prompts to show recovery status)
Next
From: Dave Cramer
Date:
Subject: Re: let's make the list of reportable GUCs configurable (was Re: Add%r substitution for psql prompts to show recovery status)