couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Smith (Commented) (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1410) Formally define number support
Date Wed, 15 Feb 2012 01:02:10 GMT


Jason Smith commented on COUCHDB-1410:

Bob, the JSON definition of number is not loose. You have numerals, a dot, numerals, an "E",
and numerals. That pretty much describes arbitrary precision decimals. Everybody keeps talking
about JSON but the crucial matter is, what does Couch do with *numbers*; or put another way,
how can we expect the JSON to *change* from a PUT to a GET.

Couch is used with instrumentation and scientific applications. Significant figures matter.
It would be nice Couch maintained them. But there are workarounds, so that is merely a nice-to-have.

Simply identifying Couch's treatment of numbers is IMHO quite fine.
> Formally define number support
> ------------------------------
>                 Key: COUCHDB-1410
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>    Affects Versions: 1.2
>            Reporter: Robert Newson
>            Priority: Blocker
>             Fix For: 1.3
> The JSON spec has a very loose definition of Number. CouchDB, as a database, should have
well-defined and first class support for numbers (both integral and decimal). The precision
of number support should be formally specified as should the algorithm used to represent floating-point
values, especially where an approximation must be made in the conversion.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message