Re: [PATCH] Generalized JSON output functions

To reiterate: for my problem, that is escaping numerics that can potentially overflow[1] under ECMAScript standard, I want to be able to override the code that outputs the numeric converted to string.  There is no way in current implementation to do that *at all*, short of copying all the code involved in producing JSON output and changing it at certain points.  One could try re-parsing JSON instead, but that doesn't actually solve the issue, because type information is lost forever at that point.

The whitespace unification was a mere side-effect of the original effort on this patch.

The dynamic type change is some what I would not to do in database, really :)

If you afraid about overflow, then convert numeric to string immediately - in this case, the client have to support both variant - so immediate cast should not be a problem.

Anyway this check on max number should be implemented in our JSON(b) out functions (as warning?).