2012/1/11 Robert Haas <robertmhaas(at)gmail(dot)com>:
> On Tue, Dec 20, 2011 at 9:06 PM, David E. Wheeler <david(at)kineticode(dot)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 data structures?
>>> 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, ...)
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
In response to
pgsql-hackers by date
|Next:||From: Benedikt Grundmann||Date: 2012-01-11 08:26:52|
|Subject: Re: random_page_cost vs seq_page_cost|
|Previous:||From: Greg Smith||Date: 2012-01-11 04:38:12|
|Subject: Re: checkpoint writeback via sync_file_range|