From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
---|---|
To: | Claes Jakobsson <claes(at)surfar(dot)nu> |
Cc: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Jan Urbański <wulczer(at)wulczer(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Joey Adams <joeyadams3(dot)14159(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>, Jan Wieck <janwieck(at)yahoo(dot)com> |
Subject: | Re: JSON for PG 9.2 |
Date: | 2011-12-21 02:06:53 |
Message-ID: | 88EBB749-A03C-434C-ADE7-20C1CCE4C887@kineticode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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?
Yes.
> if b) then this might get a lot more interesting
JSON is the most popular/likely way to represent that, I think.
David
From | Date | Subject | |
---|---|---|---|
Next Message | 高增琦 | 2011-12-21 03:34:02 | Re: why do we need create tuplestore for each fetch? |
Previous Message | David E. Wheeler | 2011-12-21 02:05:30 | Re: JSON for PG 9.2 |