> Yes, but I think the plugin is the right place to do it. What is more, this won't actually prevent you completely from producing non-ECMAScript compliant JSON, since json or jsonb values containing offending numerics won't be caught, AIUI.
Ah, that's a good catch indeed. > But a fairly simple to write function that reparsed and fixed the JSON inside the decoder would work. Need to rethink this, but reparsing was never my favorite option here. :-) -- Alex
