| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | "David E(dot) Wheeler" <david(at)kineticode(dot)com>, 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-01 19:03:28 |
| Message-ID: | 1262372608.29407.3.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On tor, 2009-12-31 at 11:12 -0500, Andrew Dunstan wrote:
>
> 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.
Whose requirement is it? I'm not ignoring it, but so far no one has
actually said that it is a requirement and why.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2010-01-01 19:12:43 | Re: Win64 warnings about size_t |
| Previous Message | Magnus Hagander | 2010-01-01 19:01:07 | Re: Win64 warnings about size_t |