Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D284ED2BC for ; Tue, 17 Jul 2012 03:32:05 +0000 (UTC) Received: (qmail 90504 invoked by uid 500); 17 Jul 2012 03:32:04 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 90310 invoked by uid 500); 17 Jul 2012 03:32:03 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 90275 invoked by uid 99); 17 Jul 2012 03:32:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jul 2012 03:32:02 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of space.ship.traveller@gmail.com designates 74.125.83.52 as permitted sender) Received: from [74.125.83.52] (HELO mail-ee0-f52.google.com) (74.125.83.52) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jul 2012 03:31:55 +0000 Received: by eeke51 with SMTP id e51so558700eek.11 for ; Mon, 16 Jul 2012 20:31:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Lt5/IEQiRbeUQ4h286RRc6iV4OFv4VVAUXUSqTUakgQ=; b=r06nugvoCQgqFf8JZVg+9/eHlqOd25degHXNCM4eNnKdz/CwjpcAkKOUwZOPEHCHZe ixgrfKUIHB56rcs3I5D54vnk2rvTFNoothAFFZQlUuns9yBNadbNUIoPMSCXGt1MJ3hg NZfvnJfIcVlJCtzl34jX9vN9mK3Ig4RCZ1FwgucoDyBpzmQ/LarIfiJP33I/qBLN0Viz +LF4a7r/Eikf4pMAwV/Z1nuLX/qWk+AGAoN72Nrgd3c50wtm1sSwNTYFKO0sLn5Gamn6 Vr4eM96VHrP7W7NA6CCRUL4jn5jtbfIvG4Rh1fC9f13omypQCzoTpJR63iLymPBrN9ZV Z8ow== MIME-Version: 1.0 Received: by 10.14.180.67 with SMTP id i43mr979242eem.23.1342495895150; Mon, 16 Jul 2012 20:31:35 -0700 (PDT) Received: by 10.14.224.1 with HTTP; Mon, 16 Jul 2012 20:31:35 -0700 (PDT) In-Reply-To: <0B6FF29B-0927-4D25-A19B-894EADCB55E2@couchbase.com> References: <966B21E1-B4F8-42CF-A266-C562AA0D7E8E@apache.org> <0B6FF29B-0927-4D25-A19B-894EADCB55E2@couchbase.com> Date: Tue, 17 Jul 2012 15:31:35 +1200 Message-ID: Subject: Re: Numerical accuracy and precision From: Samuel Williams To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=047d7b603b84f161aa04c4fe2ef1 --047d7b603b84f161aa04c4fe2ef1 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Jens, Thanks for the information. So, in light of what you've said, what is the recommended way to ensure numerical precision with CouchDB? Kind regards, Samuel On 17 July 2012 10:35, Jens Alfke wrote: > > On Jul 16, 2012, at 9:28 AM, Robert Newson rnewson@apache.org>> wrote: > > The built-in reduce functions are executed in erlang, which has arbitrary > precision for integers and 64-bit precision for floating point. > > Implementing the design document functions in Erlang would be one > workaround, although it wouldn't be allowed on a hosted CouchDB server. > > > On Jul 16, 2012, at 8:33 AM, Samuel Williams < > space.ship.traveller@gmail.com> > wrote: > > it seems like a language with built in support for big > integers would be ideal, e.g. Python, Ruby, rather than JavaScript. > > Both these languages are quite a bit slower than JavaScript, though, and > performance is often a concern for view indexing. > > =97Jens > --047d7b603b84f161aa04c4fe2ef1--