| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
| Cc: | 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: | 2009-12-31 16:12:54 |
| Message-ID: | 4B3CCD86.3030403@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David E. Wheeler wrote:
> On Dec 31, 2009, at 1:04 AM, Peter Eisentraut wrote:
>
>
>> I think the primary use will be to load a JSON value into Perl or Python
>> and process it there. So a json type that doesn't have any interesting
>> operators doesn't sound useless to me. The features I would like to get
>> out of it are input validation and encoding handling and smooth
>> integration with said languages.
>>
>
> What about access to various parts of a JSON data structure? Or is that just asking for too much trouble up-front?
>
>
>
IMNSHO it's essential. I think Peter's approach of ignoring this
requirement is extremely shortsighted.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2009-12-31 16:16:37 | Re: Serializable Isolation without blocking |
| Previous Message | fangfang liu | 2009-12-31 16:04:23 | Re: add xml support function |