Re: JSONPATH documentation
Liudmila Mantrova <l.mantrova@postgrespro.ru>
From: Liudmila Mantrova <l.mantrova@postgrespro.ru>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
Tom Lane <tgl@sss.pgh.pa.us>, Alexander Korotkov <a.korotkov@postgrespro.ru>
Cc: Jeff Janes <jeff.janes@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-09-25T14:46:08Z
Lists: pgsql-hackers
Attachments
- move-jsonpath.patch (text/x-patch) patch
On 9/25/19 12:08 AM, Peter Eisentraut wrote: > On 2019-09-23 00:03, Tom Lane wrote: >> While we're whining about this, I find it very off-putting that >> the jsonpath stuff was inserted in the JSON functions section >> ahead of the actual JSON functions. I think it should have >> gone after them, because it feels like a barely-related interjection >> as it stands. Maybe there's even a case that it should be >> its own <sect1>, after the "functions-json" section. > I'd just switch the sect2's around. As more SQL/JSON functionality gets added, I believe a separate sect1 is likely to be more justified. However, for v12 I'd vote for moving sect2 down. The patch is attached, it also fixes the ambiguous sentence that has raised questions in this thread. -- Liudmila Mantrova Technical writer at Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
Commits
-
doc: Update a confusing sentence about SQL/JSON
- a4a5c0cf9cec 13.0 landed
- baca53d3dca7 12.0 landed
-
doc: Reorder JSON functions documentation
- a083657896c7 13.0 landed
- 66e0ea75bb9d 12.0 landed