Skip site navigation (1) Skip section navigation (2)

Re: PATCH: Add hstore_to_json()

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Andrew Dunstan <andrew(at)dunslane(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:00:58
Message-ID: 863A1B07-6045-4A9C-9190-92D30BC122B3@kineticode.com (view raw or flat)
Thread:
Lists: pgsql-hackers
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

In response to

Responses

pgsql-hackers by date

Next:From: Magnus HaganderDate: 2009-12-31 16:03:37
Subject: uintptr_t for Datum
Previous:From: Simon RiggsDate: 2009-12-31 15:58:45
Subject: Re: Cancelling idle in transaction state

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group