Re: jsonb and nested hstore

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Oleg Bartunov <obartunov(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Christophe Pettus <xof(at)thebuild(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: jsonb and nested hstore
Date: 2014-03-06 17:48:58
Message-ID: CAHyXU0wHXxrgPntQo4QXFcdsx62_20=CfW91q+Bjeq1H1+9Dww@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 6, 2014 at 11:28 AM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
> So here my opinion on what we should do:
>
> 1. Forget about hstore2
> 2. Add GIN and GIST operator classes to jsonb, if they're ready for commit
> pretty darn soon. If not, punt them to next release.

For #2, would we maintain the hstore syntax for the searching
operators. For example,

SELECT count(*) FROM jsonb_schema WHERE tabledata @> 'columns =>
{{column_name=>total_time}}';

Note the hstore-ish => in the searching operator.

merlin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleg Bartunov 2014-03-06 17:50:56 Re: jsonb and nested hstore
Previous Message Tom Lane 2014-03-06 17:44:34 Re: Securing "make check" (CVE-2014-0067)