| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Ronan Dunklau <ronan(dot)dunklau(at)dalibo(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>, 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>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Christophe Pettus <xof(at)thebuild(dot)com> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-03-07 04:35:19 |
| Message-ID: | 20140307043519.GH11419@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2014-03-07 04:52:22 | Re: Securing "make check" (CVE-2014-0067) |
| Previous Message | Bruce Momjian | 2014-03-07 04:33:13 | Re: jsonb and nested hstore |