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

From Alexander Korotkov
Subject Re: SQL/JSON path issues/questions
Date
Msg-id CAPpHfdsSW2ULL3cYowLWwMV=FGBFQ2H5NYRZ0dyN9YJ5GAsqdg@mail.gmail.com
Whole thread Raw
In response to Re: SQL/JSON path issues/questions  (Thom Brown <thom@linux.com>)
Responses Re: SQL/JSON path issues/questions
List pgsql-hackers
On Thu, Jul 11, 2019 at 5:10 PM Thom Brown <thom@linux.com> wrote:
> 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 <.

Thank you for catching this!  Fix just pushed.

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [Proposal] Table-level Transparent Data Encryption (TDE) and KeyManagement Service (KMS)
Next
From: Rafia Sabih
Date:
Subject: Fwd: [HACKERS] [WIP] Effective storage of duplicates in B-tree index.