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? Best, David -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers