Re: JSONPATH documentation
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Korotkov <a.korotkov@postgrespro.ru>
Cc: Jeff Janes <jeff.janes@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-09-22T22:03:32Z
Lists: pgsql-hackers
Alexander Korotkov <a.korotkov@postgrespro.ru> writes: > On Sun, Sep 22, 2019 at 9:18 PM Jeff Janes <jeff.janes@gmail.com> wrote: > Currently description of jsonpath is divided between datatypes section > and functions and operators section. And yes, this looks cumbersome. Agreed, but ... > I think we should move the whole description to the one section. > Probably we should move jsonpath description to datatypes section > (assuming jsonpath is a datatype) leaving functions and operators > section with just SQL-level functions and operators. What do you > think? ... I don't think that's an improvement. We don't document detailed behavior of a datatype's functions in datatype.sgml, and this seems like it would be contrary to that layout. If anything, I'd merge the other way, with only a very minimal description of jsonpath (perhaps none?) in datatype.sgml. 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. regards, tom lane
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