[ 
https://issues.apache.org/jira/browse/COUCHDB-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Shorin closed COUCHDB-724.
------------------------------------

    Resolution: Fixed

Close as fixed since I'm not able to reproduce this issue with actual CouchDB 
releases: 1.2.0 (not much, but still), 1.2.2, 1.3.0 and master. Much lucky it 
was eventually fixed with COUCHDB-1118 by [adding ejson 
application|https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=commit;h=3925e856078717a4b3c1ed58918a11cf90a758b9].
                
> Big numbers changed to decimals
> -------------------------------
>
>                 Key: COUCHDB-724
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-724
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 0.11
>         Environment: Mac OS X running 
> CouchDBX-0.11.0-R13B04-64bit-Snow-Leopard
>            Reporter: Matthew Sinclair-Day
>
> After upgrading from Couch 0.10.1 to 0.11.0, big integers are now being 
> returned by couch as decimals.  This is a change from the previous release.
> Here's a curl session demonstrating the problem:
> curl -X POST http://localhost:5984/msdtest -d '{"num":123456789123456789}'
> {"ok":true,"id":"8d211c89d80d14972af7cb93e71754bc","rev":"1-fce9e6cc4e72866f75aeadbaed1a65c9"}
> curl http://localhost:5984/msdtest/8d211c89d80d14972af7cb93e71754bc
> {"_id":"8d211c89d80d14972af7cb93e71754bc","_rev":"1-fce9e6cc4e72866f75aeadbaed1a65c9","num":123456789123456780.0}
> In Futon, the 'num' value does not have a decimal.
> It seems like the problem occurs with large numbers.  Here's another curl
> where the num is not made into a decimal:
> curl -X POST http://localhost:5984/msdtest -d '{"num":123456789}'
> {"ok":true,"id":"8d211c89d80d14972af7cb93e7175daf","rev":"1-039a59b36e40b4216eac91872eed4645"}
> curl http://localhost:5984/msdtest/8d211c89d80d14972af7cb93e7175daf
> {"_id":"8d211c89d80d14972af7cb93e7175daf","_rev":"1-039a59b36e40b4216eac91872eed4645","num":123456789}
> Here's a session from 0.10.1 demonstrating the problem did not exist in that 
> release:
> curl -X POST http://localhost:5984/msdtest -d '{"num":123456789123456789}'
> {"ok":true,"id":"fcd6d8fca421023581a608758a0abe35","rev":"1-fce9e6cc4e72866f75aeadbaed1a65c9"}
> curl http://localhost:5984/msdtest/fcd6d8fca421023581a608758a0abe35
> {"_id":"fcd6d8fca421023581a608758a0abe35","_rev":"1-fce9e6cc4e72866f75aeadbaed1a65c9","num":123456789123456789}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to