Re: SQL/JSON path issues/questions

Alexander Korotkov <a.korotkov@postgrespro.ru>

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-07T21:30:01Z

Lists: pgsql-hackers

Attachments

0004-clarify-jsonpath-docs-5.patch (application/octet-stream) patch 0004

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.

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

Commits

Fixes for jsonpath filter expression elements table in docs
- 1ed89826b82c 12.0 landed
- 0cea6eb5a5f2 13.0 landed
Assorted fixes for jsonpath documentation
- a5c2f3a346fc 12.0 landed
- 5a7d697a3936 13.0 landed
Fix description for $varname jsonpath variable
- dfd79e2d0e8f 12.0 landed
Improve documentation for jsonpath like_regex predicate
- 1ff8dc9f19dd 12.0 landed
Support 'q' flag in jsonpath 'like_regex' predicate
- 261a5c192856 12.0 landed