Re: SQL/JSON path issues/questions
Alexander Korotkov <a.korotkov@postgrespro.ru>
From: Alexander Korotkov <a.korotkov@postgrespro.ru>
To: Steven Pousty <steve.pousty@gmail.com>
Cc: Thom Brown <thom@linux.com>,
Liudmila Mantrova <l.mantrova@postgrespro.ru>, Kyotaro Horiguchi <horikyota.ntt@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2019-07-20T18:48:07Z
Lists: pgsql-hackers
Hi Steven, On Fri, Jul 19, 2019 at 9:53 PM Steven Pousty <steve.pousty@gmail.com> wrote: > I would like to help review this documentation. Can you please point me in the right direction? Thank you for your interest. You're welcome to do review. Please take a look at instruction for reviewing a patch [1] and working with git [2]. Also, in order to build a doc you will need to setup a toolset first [3]. Links 1. https://wiki.postgresql.org/wiki/Reviewing_a_Patch 2. https://wiki.postgresql.org/wiki/Working_with_git#Testing_a_patch 3. https://www.postgresql.org/docs/devel/docguide-toolsets.html ------ 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