Re: jsonb and nested hstore

On Fri, Feb 28, 2014 at 1:25 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> The only "dependency" is if you want to be able to use some advanced
> indexing and other functionality, for which we don't currently have jsonb
> equivalents of the new hstore operators, because we ran out of time. Then
> you can get this functionality by casting the data to hstore (assuming we
> also have nested-hstore committed) and using its operators. But that's no
> more a dependency than it is for any other type for which you can leverage
> this functionality (e.g. any record type).

I don't think hstore-style indexing is "advanced"; it's the main
reason for there being a jsonb, in my view. Anyway, this is where I
have a hard time understanding what you intend for jsonb for 9.4. You
ran out of time for writing jsonb operator classes, and so you can use
the hstore ones, which work fine. But, if we didn't run out of time,
how would the jsonb operator classes differ from the hstore ones? Is
there something inferior about the hstore operator class as compared
to a hypothetical jsonb operator class, other than the superficial
need to cast?

--
Peter Geoghegan