Re: SQL/JSON path issues/questions

On Thu, Jul 11, 2019 at 5:10 PM Thom Brown <thom(at)linux(dot)com> wrote:
> On Wed, 10 Jul 2019 at 05:58, Alexander Korotkov
> <a(dot)korotkov(at)postgrespro(dot)ru> wrote:
> >
> > On Mon, Jul 8, 2019 at 12:30 AM Alexander Korotkov
> > <a(dot)korotkov(at)postgrespro(dot)ru> wrote:
> > > On Thu, Jul 4, 2019 at 4:38 PM Liudmila Mantrova
> > > <l(dot)mantrova(at)postgrespro(dot)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