Re: jsonb and nested hstore

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: jsonb and nested hstore
Date: 2014-01-28 16:00:54
Message-ID: 52E7D436.8080002@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


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).

If that's not correct I'll change it, but that's what I read here:
<http://oreilly.com/openbook/docbook/book/entry.html>

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-01-28 16:09:34 Re: jsonb and nested hstore
Previous Message Tom Lane 2014-01-28 16:00:23 Re: alternative back-end block formats