Re: jsonb and nested hstore - Mailing list pgsql-hackers

From Tom Lane
Subject Re: jsonb and nested hstore
Date
Msg-id 23256.1390925374@sss.pgh.pa.us
Whole thread Raw
In response to Re: jsonb and nested hstore  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: jsonb and nested hstore  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: jsonb and nested hstore  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.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.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: jsonb and nested hstore
Next
From: Christian Kruse
Date:
Subject: Re: [PATCH] Use MAP_HUGETLB where supported (v3)