From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
Cc: | Liudmila Mantrova <l(dot)mantrova(at)postgrespro(dot)ru>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SQL/JSON path issues/questions |
Date: | 2019-07-11 14:09:28 |
Message-ID: | CAA-aLv4Tggy6Z3kaG9n+3SHwOVGN2Yj_MJXfdfwjH_jBNZzJNA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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 <.
Thom
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2019-07-11 14:10:00 | Re: let's make the list of reportable GUCs configurable (was Re: Add %r substitution for psql prompts to show recovery status) |
Previous Message | Robert Haas | 2019-07-11 14:06:23 | Re: let's make the list of reportable GUCs configurable (was Re: Add %r substitution for psql prompts to show recovery status) |