Re: jsonb and nested hstore

On Wed, Mar 5, 2014 at 11:24 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
>>>> *All* non-sql standard types ought to be in extensions in an ideal world.
>
> While there's certainly much to be said for the idea that jsonb should be
> an extension, I don't think we have the technology to package it as a
> *separate* extension; it'd have to be included in the hstore extension.
> Which is weird, and quite a mixed message from the marketing standpoint.
> If I understand Josh's vision of the future, he's expecting that hstore
> will gradually die off in favor of jsonb, so we don't really want to
> present the latter as the ugly stepchild.
>
> Just out of curiosity, exactly what features are missing from jsonb
> today that are available with hstore? How long would it take to
> copy-and-paste all that code, if someone were to decide to do the
> work instead of argue about it?

I believe the main thing is the opclasses.

My information might be incomplete.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company