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 <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
