| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PATCH: Add hstore_to_json() |
| Date: | 2010-01-03 18:51:22 |
| Message-ID: | B439FD39-183A-4DBA-967D-E8CAF86E0196@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jan 3, 2010, at 8:00 AM, Andrew Dunstan wrote:
> I think the minimal functionality I'd want is:
>
> convert record to JSON
> convert JSON to record
With caveats as to dealing with nested structures (can a record be an attribute of a record?).
> extract a value, or set of values, from JSON
> composition of JSON
There's a lot of functionality in hstore that I'd like to see. It'd make sense to use the same operators for the same operations. I think I'd start with hstore as a basic spec.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2010-01-03 18:53:34 | Re: Testing with concurrent sessions |
| Previous Message | Andrew Dunstan | 2010-01-03 17:44:32 | Re: invalid UTF-8 via pl/perl |