From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: jsonb and nested hstore |
Date: | 2014-01-28 16:09:34 |
Message-ID: | 23256.1390925374@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Christian Kruse | 2014-01-28 16:11:11 | Re: [PATCH] Use MAP_HUGETLB where supported (v3) |
Previous Message | Andrew Dunstan | 2014-01-28 16:00:54 | Re: jsonb and nested hstore |