On Sun, Feb 12, 2012 at 18:30, Robert Newson <[email protected]> wrote: > I'm in favor of adding it to breaking changes and keeping the new > behaviour. Both ejson and jiffy use %g to encode numbers. This favors > a shorter encoding. On reflection, this is more desirable than > pretending that json distinguishes between ints and floats.
JSON does distinguish between those: a JSON number that includes a "." character obviously denotes a float, while one with a "." character denotes an integer. The JSON spec does not include any information on how numbers are to be interpreted, so CouchDB should try to refrain from guessing. Cheers, Dirkjan
