couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Smith <>
Subject Re: [VOTE] Apache CouchDB 1.2.0 release, first round
Date Mon, 13 Feb 2012 00:18:53 GMT
On Mon, Feb 13, 2012 at 12:30 AM, Robert Newson <> 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.

Hi, Bob. Do you remember grade school science class? 1 is not the same
as 1.0, because the latter is a value with two significant figures.

When CouchDB is used with instrumentation and laboratory data, people
may care that 1.0 remains just so. Their data is not the real number
one, but the JSON expression one point zero.

Noah, "JSON" can no more mess up your numbers than utf-8 can. It is
simply an encoding format with no inherent size restriction. The issue
is whether *CouchDB* is messing up numbers through a decode/encode

Iris Couch

View raw message