Horton

Re: SQL/JSON path issues/questions

Alexander Korotkov <a.korotkov@postgrespro.ru>

View thread View on postgr.es
From: Alexander Korotkov <a.korotkov@postgrespro.ru>
To: Liudmila Mantrova <l.mantrova@postgrespro.ru>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>, Thom Brown <thom@linux.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2019-07-10T04:58:26Z
Lists: pgsql-hackers 
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!

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

Commits

  1. Fixes for jsonpath filter expression elements table in docs

  2. Assorted fixes for jsonpath documentation

  3. Fix description for $varname jsonpath variable

  4. Improve documentation for jsonpath like_regex predicate

  5. Support 'q' flag in jsonpath 'like_regex' predicate