Re: JSONPATH documentation - Mailing list pgsql-hackers

From Liudmila Mantrova
Subject Re: JSONPATH documentation
Date
Msg-id deef0e68-ef0b-80f3-9359-a493f2be4575@postgrespro.ru
Whole thread Raw
In response to Re: JSONPATH documentation  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: JSONPATH documentation  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
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


Attachment

pgsql-hackers by date:

Previous
From: Muhammad Usama
Date:
Subject: Proposal for syntax to support creation of partition tables whencreating parent table
Next
From: Anastasia Lubennikova
Date:
Subject: Re: [HACKERS] [WIP] Effective storage of duplicates in B-tree index.