couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roger Binns <>
Subject Re: Silent corruption of large numbers
Date Mon, 09 Nov 2009 20:20:11 GMT
Hash: SHA1

Brian Candler wrote:
>> I don't know what the right solution to this is.
> One option: store the values as strings.

I meant the right solution for CouchDB.  For example it could take a lowest
common denominator approach and reject all documents whose contents cannot
be correctly represented by all "supported" view engines.  Or it could
require view engines to generate an error when they lose data.  Or it could
just blindly keep soldiering on and make it the problem of the user (current

Although this is an issue with integers it can also be the case with
strings.  An earlier post linked to JSON discussion where it wasn't exactly
clear if a JSON string actually has to be valid or is just a list of
unsigned 16 bit integers.  And what about view engines whose internals have
a length limit on strongs?

> Another option: use the Erlang view server,

Not an option as my code is a library for others to use.

> and get a big view-building speed boost for free too.

The biggest performance benefit for me would be if as many copies of the
Javascript external process were run as I have processor cores.  It is quite
frustrating watching one core be 100% busy and the other 0% busy while a
view is being built.

Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla -


View raw message