Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion decimal field using sqlite

Received: by 10.50.163.97 with SMTP id yh1mr599849igb.3.1334007945231;
        Mon, 09 Apr 2012 14:45:45 -0700 (PDT)
X-BeenThere: datamapper@googlegroups.com
Received: by 10.231.80.134 with SMTP id t6ls4585490ibk.8.gmail; Mon, 09 Apr
 2012 14:45:44 -0700 (PDT)
Received: by 10.68.233.70 with SMTP id tu6mr281747pbc.3.1334007943963;
        Mon, 09 Apr 2012 14:45:43 -0700 (PDT)
Date: Mon, 9 Apr 2012 14:45:43 -0700 (PDT)
From: "Dan Kubb (dkubb)" <dan.k...@gmail.com>
To: datamapper@googlegroups.com
Message-ID: <29111911.14.1334007943432.JavaMail.geo-discussion-forums@pbky1>
In-Reply-To: <c81bb827-1b9d-4512-bd6d-126d0ec3cdef@f27g2000yqc.googlegroups.com>
References: <c81bb827-1b9d-4512-bd6d-126d0ec3cdef@f27g2000yqc.googlegroups.com>
Subject: Re: decimal field using sqlite
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_12_19119212.1334007943431"

------=_Part_12_19119212.1334007943431
Content-Type: multipart/alternative; 
	boundary="----=_Part_13_1173243.1334007943431"

------=_Part_13_1173243.1334007943431
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi Arthur,

It just occurred to me that this could also be a problem with SQLite 
storing the data using a double precision floating point column behind the 
scenes. If that's so, then there could be a loss of accuracy, and it would 
be possible for the value you write to the database is not the same as what 
is returned.

I'm still operating under the assumption that DM or DO is responsible for 
this, but it may end up this is a result of something outside of our 
control.

-- 

Dan 

------=_Part_13_1173243.1334007943431
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

Hi Arthur,<br><br>It just occurred to me that this could also be a problem with SQLite storing the data using a double precision floating point column behind the scenes. If that's so, then there could be a loss of accuracy, and it would be possible for the value you write to the database is not the same as what is returned.<div><br></div><div>I'm still operating under the assumption that DM or DO is responsible for this, but it may end up this is a result of something outside of our control.</div><div><br></div><div>--&nbsp;<br><div><br></div><div>Dan&nbsp;</div></div>
------=_Part_13_1173243.1334007943431--

------=_Part_12_19119212.1334007943431--