On Thu, Mar 6, 2014 at 04:33:08PM +0100, Ronan Dunklau wrote:
> > I'm not sure what the constraints of json that you might want to break
> > are. Perhaps you'd like to specify.
>
> I haven't followed the whole thread, but json is really restrictive on the
> supported types: a hierarchical hstore could maybe support more types
> (timestamp comes to mind) as its values, which is not a valid data type in the
> json spec.
Yes, I can see this as an idea for a new data type that allows
hierarchical storage of key/value pairs where the value can be any
Postgres data type. It wouldn't be called hstore, or hstore2, but
something else.
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ Everyone has their own god. +