Alvaro Herrera <alvhe...@commandprompt.com> writes:
> Tom Lane escribió:
>> Well, actually, now that you mention it: how much of a json type would
>> be duplicative of the xml stuff? Would it be sufficient to provide
>> json <-> xml converters and let the latter type do all the heavy lifting?
>> (If so, this patch ought to be hstore_to_xml instead.)
> But then there's the matter of overhead: how much would be wasted by
> transforming to XML, and then parsing the XML back to transform to JSON?
Well, that would presumably happen only when sending data to or from the
client. It's not obvious that it would be much more expensive than the
syntax checking you'd have to do anyway.
If there's some reason to think that operating on json data would be
much less expensive than operating on xml, there might be a case for
having two distinct sets of operations internally, but I haven't heard
anybody make that argument.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
