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

Re: is JSON really "a type" (Re: data to json enhancements)

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Hannu Krosing <hannu(at)krosing(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: is JSON really "a type" (Re: data to json enhancements)
Date: 2012-09-29 21:29:12
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On 09/29/2012 05:01 PM, Hannu Krosing wrote:
> On 09/29/2012 05:40 PM, Andrew Dunstan wrote:
>> I still think Tom's suggestion is the best and simplest way to do that.
> which Toms suggestion you mean here ?
> The 3. mentioned above was for making possible 2 separate ways to 
> convert (serialise/quote/escape and parse/check-for-valid-json) string 
> to json and afair not about hstore to json.

Er, what? yes, I meant option 3, and it is a perfect mechanism for doing 
conversion of an hstore field inside datum_to_json: the code would look 
for a cast to the new type (whatever we call it) and use that instead of 
the normal text representation.

> I'm also looking forward for an easy way or two to populate a record 
> from json and extract an array from json.

I am prepared to take this on - at least starting with json to array 
which I think is the simpler case. I have some ideas about how to do 
this and have done a bit of experimental work along these lines. 
Personally I'd be inclined to make it do a conversion to text[] and then 
cast from that to anything else we needed.



In response to


pgsql-hackers by date

Next:From: Andrew DunstanDate: 2012-09-29 21:52:03
Subject: Re: pg_upgrade tests vs alter generic changes
Previous:From: Hannu KrosingDate: 2012-09-29 21:01:58
Subject: Re: is JSON really "a type" (Re: data to json enhancements)

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