Re: jsonb and nested hstore

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: jsonb and nested hstore
Date: 2014-01-28 16:22:23
Message-ID: 20140128162223.GO10723@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > On 01/28/2014 10:50 AM, Alvaro Herrera wrote:
> > + </indexterm><indexterm>
> > + <primary>jsonb_each</primary>
> > + </indexterm><para><literal>json_each(json)</literal>
> > + </para><para><literal>jsonb_each(jsonb)</literal>
> > + </para></entry>
> >> This SGML nesting is odd and hard to read. Please place opening tags in
> >> separate lines (or at least not immediately following a closing tag). I
> >> am not sure whether the mentions of jsonb_each vs. json_each there are
> >> correct or typos. This also occurs in other places.
>
> > As I understand it, an <entry> tag can only contain block-level elements
> > like <para> if there are no inline elements (including white space).
>
> Practically every existing use of <indexterm> is freer than this in its
> use of whitespace. It sounds to me like maybe you are trying to put the
> <indexterm> inside something it shouldn't go inside of.

FWIW I was just talking about formatting of the SGML source so that it
is easier to read.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2014-01-28 16:26:16 Re: jsonb and nested hstore
Previous Message Tom Lane 2014-01-28 16:20:39 Re: A minor correction in comment in heaptuple.c