From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Korotkov <a.korotkov@postgrespro.ru>
Cc: Jeff Janes <jeff.janes@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: JSONPATH documentation
Date: Tue, 24 Sep 2019 23:08:25 +0200
Message-ID: <96fb58c4-6281-b201-b900-03d0a84f77ac@2ndquadrant.com> (raw)
In-Reply-To: <16968.1569189812@sss.pgh.pa.us>
References: <CAMkU=1wP-SO4KpiLxHJuPezTJCmK=JqefLXrr3eXFO7Qku+tMg@mail.gmail.com>
<CAPpHfdvYektyqQp-On+dbqO7GV_h=59y=6yGxUm4Pisc2PcDjg@mail.gmail.com>
<16968.1569189812@sss.pgh.pa.us>
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.
That would be similar to how the documentation of regular expressions is
laid out: functions first, then details of the contained mini-language.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, tgl@sss.pgh.pa.us, a.korotkov@postgrespro.ru, jeff.janes@gmail.com
Subject: Re: JSONPATH documentation
In-Reply-To: <96fb58c4-6281-b201-b900-03d0a84f77ac@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox