Re: jsonb and nested hstore

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru>
Subject: Re: jsonb and nested hstore
Date: 2014-02-25 17:45:10
Message-ID: 20140225174510.GC1507@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 25, 2014 at 09:38:50AM -0800, Josh Berkus wrote:
> > In short, I think you're viewing everything about jsonb with
> > rose-colored glasses on, and that your enthusiasm is mostly wishful
> > thinking. Will there be good things about jsonb? Of course. Will
> > lots of people want to use it for those reasons? Very likely. Will
> > it be better than json in all ways and for all purposes? No, and
> > implying the contrary is just plain wrong.
>
> It hurts our adoption substantially to confuse developers. We need to
> recommend one type over the other, hence "Use jsonb unless you need X".
> Merlin is pushing the type of multivariable comparison where *I*
> wouldn't be able to make sense of which one I should pick, let alone
> some web developer who's just trying to get a site built. That sort of
> thing *really* doesn't help our users.

I agree it would be nice to have something simple, like "Use JSON if you
wish to just store/retrieve entire JSON structures, and JSONB if you
wish to do any kind of lookup or manipulation of JSON values on the
server".

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-02-25 18:15:09 Avoiding deeply nested AND/OR trees in the parser
Previous Message Bruce Momjian 2014-02-25 17:39:34 Re: [PATCH] Use MAP_HUGETLB where supported (v3)