Re: JSON for PG 9.2 - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: JSON for PG 9.2
Date
Msg-id CAFj8pRCsG9D2SWgk6PObW8ArkrzfP6KXaydjXhhKr4K-D56hXw@mail.gmail.com
Whole thread Raw
In response to Re: JSON for PG 9.2  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: JSON for PG 9.2  (Andrew Dunstan <andrew@dunslane.net>)
Re: JSON for PG 9.2  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
2012/1/11 Robert Haas <robertmhaas@gmail.com>:
> On Tue, Dec 20, 2011 at 9:06 PM, David E. Wheeler <david@kineticode.com> wrote:
>> On Dec 20, 2011, at 10:39 AM, Claes Jakobsson wrote:
>>> Are people explicitly asking for a) *JSON* datatype or b) a type that lets you store arbitrary complex semi-untyped
datastructures?
 
>>
>> Yes.
>>
>>> if b) then this might get a lot more interesting
>>
>> JSON is the most popular/likely way to represent that, I think.
>
> On that note, here's an updated version of the patch I posted
> upthread, with some regression tests and minimal documentation.

I like this patch and this feature.

I see only one issue - there is not functionality that helps generate
JSON in pg.

What do you think about functions: array_to_json(anyarray),
row_to_json(any) and format_json(text, text, ...)

Regards

Pavel

>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>


pgsql-hackers by date:

Previous
From: Greg Smith
Date:
Subject: Re: checkpoint writeback via sync_file_range
Next
From: Benedikt Grundmann
Date:
Subject: Re: random_page_cost vs seq_page_cost