| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Liudmila Mantrova <l(dot)mantrova(at)postgrespro(dot)ru>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: JSONPATH documentation |
| Date: | 2019-09-26 14:38:44 |
| Message-ID: | 83d5bb74-9c47-76a5-0c81-6b1c19421288@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-09-25 16:46, Liudmila Mantrova wrote:
> 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.
committed, thanks
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2019-09-26 14:43:33 | Re: PostgreSQL12 and older versions of OpenSSL |
| Previous Message | Pavel Stehule | 2019-09-26 14:36:36 | Re: dropdb --force |