couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebastian Cohnen (JIRA)" <>
Subject [jira] Commented: (COUCHDB-749) CouchDB does not persist large values of Numbers correctly.
Date Sat, 24 Apr 2010 17:21:49 GMT


Sebastian Cohnen commented on COUCHDB-749:

I would vote for (a). If CouchDB (or any parts of it like spidermonkey) cannot handle integers
above a certain size, they should be rejected. if developer need to store bigger values, they
are still free to encode them differently (like using strings).

> CouchDB does not persist large values of Numbers correctly.
> -----------------------------------------------------------
>                 Key: COUCHDB-749
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 0.11
>         Environment: All
>            Reporter: Jarrod Roberson
> All the following operations exhibit the same bug, large numbers don't get persisted
correctly. They get something added to them for some reason.
> 9223372036854775807 == java.lang.Long.MAX_VALUE
> 1: go into Futon, create a new document and create a new field and enter the number 9223372036854775807,
click the green check mark, the number changes to 9223372036854776000 even before you save
> 2.curl -X PUT http://localhost:5984/test/longTest -d '{"value": 9223372036854775807}',
the number gets persisted as 9223372036854776000
> trying to persist System.currentTimeMilliseconds() from java causes the same thing to
happen occasionally.
> This seems to be a pretty serious bug if I can't trust that my data is not being corrupted
when submitted to the database.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message