From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 17:58:20 |
Message-ID: | CAHyXU0yeoVZ8yMOVAn8y-LbqQ4syrkARYX1y9_vgMAZzT1mf6w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jan 28, 2014 at 10:46 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
> On 01/28/2014 11:29 AM, Tom Lane wrote:
>>
>> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>>>
>>> The problem is not the indexterm element, it's the space that might
>>> exist outside it. Are we using block level elements like <para> inside
>>> entry elements anywhere else?
>>
>> Probably not, and I wonder why you're trying to. Whole paras inside
>> a table entry (this is a table no?) don't sound like they are going
>> to lead to nice-looking results.
>
> See <http://developer.postgresql.org/~adunstan/functions-json.html>
yeah. note: I think the json documentation needs *major* overhaul. too
much is going in inside the function listings where there really
should be a big breakout discussing the "big picture" of json/jsonb
with examples of various use cases. I want to give it a shot but
unfortunately can not commit to do that by the end of the 'fest.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2014-01-28 18:03:14 | Re: [PATCH] Support for pg_stat_archiver view |
Previous Message | Simon Riggs | 2014-01-28 17:54:53 | Re: ALTER TABLE lock strength reduction patch is unsafe |