Re: PATCH: Add hstore_to_json()

Peter Eisentraut <peter_e@gmx.net>

From: Peter Eisentraut <peter_e@gmx.net>

To: Andrew Dunstan <andrew@dunslane.net>

Cc: "David E. Wheeler" <david@kineticode.com>, Robert Haas <robertmhaas@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2010-01-01T19:03:28Z

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.