[
https://issues.apache.org/jira/browse/COUCHDB-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208478#comment-13208478
]
Robert Newson commented on COUCHDB-1410:
----------------------------------------
I appreciate that the format is fully defined. Perhaps what I mean, instead, is
the precision with which those numbers can be manipulated in view servers? I've
certainly been stung by some crazy number rounding issues in the past, I don't
think it's reasonable behavior for a database.
It sounds like this ticket is really two issues, 1) numbers can roundtrip
safely to and from JSON, 2) numbers can be computed with within known (and
consistent) bounds.
Issue 1 is something we need to resolve in ejson for the 1.2.0 release but
sounds simple. To fulfill this ticket, we have to commit to not breaking
roundtrip safety in future versions.
Issue 2, I suspect, is contentious. Or, at least, I suspect I desire stronger
numeric handling than javascript typically delivers. I'll be happy here if we
document, and preserve, some minimal standard.
/ramble
> Formally define number support
> ------------------------------
>
> Key: COUCHDB-1410
> URL: https://issues.apache.org/jira/browse/COUCHDB-1410
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
