Re: jsonb and nested hstore

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: Craig Ringer <craig(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru>
Subject: Re: jsonb and nested hstore
Date: 2014-02-28 02:27:01
Message-ID: 20140228022700.GV2921@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Peter Geoghegan (pg(at)heroku(dot)com) wrote:
> On Thu, Feb 27, 2014 at 6:08 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> > Extensions can't depend on other extensions directly- hence you can't
> > write an extension that depends on hstore, which sucks. It'd be
> > preferrable to not have that issue w/ json/jsonb/whatever.
>
> I think it depends of what you mean by "depend". The earthdistance
> extension "requires" 'cube', for example, "a data type cube for
> representing multidimensional cubes". Although I am aware of the
> lengths that drivers like psycopg2 go to to support hstore because
> it's an extension, which is undesirable.

What earthdistance does is simply use the 'cube' data type- that's quite
different from needing to be able to make calls from one .so into the
other .so directly. With earthdistance/cube, everything goes through
PG.

Thanks,

Stephen

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2014-02-28 02:44:48 Re: tests for client programs
Previous Message Peter Geoghegan 2014-02-28 02:17:53 Re: jsonb and nested hstore