From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: jsonb and nested hstore |
Date: | 2014-01-28 18:29:33 |
Message-ID: | CAHyXU0ymmLMVPOUkyTzPo-VLE1uyxTi=MtUraEfFF6ce5YfxPw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jan 28, 2014 at 12:09 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 01/28/2014 09:58 AM, Merlin Moncure wrote:
>> 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.
>
> FWIW, I've promised Andrew that I'll overhaul this by the end of beta.
> Given that we have all of beta for doc refinements.
>
> In addition to this, the JSON vs JSONB datatype page really needs
> expansion and clarification.
right: exactly. I'd be happy to help (such as I can) ...I wanted to
see if jsonb to make it in on this 'fest (doc issues notwithstanding);
it hasn't been formally reviewed yet AFAICT. So my thinking here is
to get docs to minimum acceptable standards in the short term and
focus on the structural code issues for the 'fest (if jsonb slips then
it's moot obviously).
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Christian Convey | 2014-01-28 18:33:18 | Re: alternative back-end block formats |
Previous Message | Alvaro Herrera | 2014-01-28 18:22:41 | Re: new json funcs |