| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PATCH: Add hstore_to_json() |
| Date: | 2010-01-05 04:18:36 |
| Message-ID: | 603c8f071001042018l79bca0e2yb990a108b0bfd830@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jan 3, 2010 at 1:51 PM, David E. Wheeler <david(at)kineticode(dot)com> wrote:
> 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.
David,
Is this something you are planning to work on for the 2010-01-15
CommitFest? If not, I think we should go ahead and mark the patch
which was the original subject of this thread "Returned with
Feedback", as it does not seem to make sense to add it unless we add a
json type first.
Thoughts?
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-01-05 04:32:36 | Index-only scans will not be in PG 8.5 |
| Previous Message | Robert Haas | 2010-01-05 04:12:55 | Re: quoting psql varible as identifier |