On Tue, Jun 24, 2014 at 9:08 AM, Andrew Dunstan <andrew@dunslane.net> wrote:
> w.r.t. json arrays, I think you're chasing a chimera, since they are
> heterogenous, unlike SQL arrays.
But, there are many useful cases where the json is known to be well
formed, right? Or do you mean that the difficulties stem from simply
validating the type? Basically, I'm wondering if
SELECT to_json(foo_t[])
is ever going to be able to be reversed by:
SELECT array(json[b]_populate_recordset(null::foo_t[]), '...'::json[b])
...where foo_t is some arbitrarily complex nested type. even simpler
(although not necessarily faster) would be:
SELECT from_json(null::foo_t[], ',,,');
or even
SELECT '...'::foo_t[]::json::foo_t[];
My basic gripe with the json[b] APIs is that there is no convenient
deserialization reverse of to_json. Tom's proposal AIUI, in particular
having internal json arrays force to json, would foreclose the last
two cases from ever being possible.
merlin