Andrew Dunstan <and...@dunslane.net> writes: > Let me just point out two things. First, we are approaching a beta release. > The time for changing this is long since gone, IMNSHO.
This is our last chance to get it right, so that argument doesn't seem to me to carry a lot of weight ... > Second, RFC 4627 is absolutely clear: a valid JSON value can only be an > object or an array, so this thing about converting arbitrary datum values > to JSON is a fantasy. If anything, we should adjust the JSON input routines > to disallow anything else, rather than start to output what is not valid > JSON. ... but this one does. regards, tom lane -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers