Date: Mon, 17 Oct 2022 15:21:53 -0400
From: Bruce Momjian <bruce@momjian.us>
To: alex.denman@nih.gov, pgsql-docs@lists.postgresql.org
Subject: Re: JSON/JSONB documentation, aggregate functions
Message-ID: <Y02rUd4bo0uvsKO/@momjian.us>
References: <166335888474.659.16897487975376230364@wrigleys.postgresql.org>
 <Y0WQRd/W94CuevdX@momjian.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Y0WQRd/W94CuevdX@momjian.us>
Archived-At: 
 <https://www.postgresql.org/message-id/Y02rUd4bo0uvsKO/%40momjian.us>
Precedence: bulk

On Tue, Oct 11, 2022 at 11:48:21AM -0400, Bruce Momjian wrote:
> On Fri, Sep 16, 2022 at 08:08:04PM +0000, PG Doc comments form wrote:
> > Regarding the Json documentation (9.16.1: processing and creating JSON
> > data), I would like to suggest that the reference to
> > json_agg/jsonb_agg/json_object_agg/jsonb_object_agg (section 9.21) be made
> > more prominent. When looking through the list of json[b] processing
> > functions, it's really easy to miss the footnote mentioning the aggregate
> > functions. The list of functions in table 9.47 includes a lot of functions
> > that are *really*similar in purpose to the json aggregator functions, and
> > it's easy to assume that anything related to building JSON[B] objects *must*
> > be listed there. I just spent hours searching for a way to turn one column
> > of keys and one column of values into a JSONB object (without coercing all
> > numeric values to json strings), and I can't imagine I'm the only one.
> 
> I see your point --- that the aggregate sentence is at the end of the
> section, after four massive tables.  The attached patch moves the
> paragraph up to the end of the section's introductory paragraph.

Patch applied back to PG 10, thanks.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Indecision is a decision.  Inaction is an action.  Mark Batterson