When can we expect a 3.2.2 release that includes this correction? I am
working on a database that depends on 64-bit integer values.
-ken
On 15-Apr-05, at 7:35 AM, D. Richard Hipp wrote:
On Fri, 2005-04-15 at 10:53 +0100, Richard Boulton wrote:
I'm running the latest sqlite 3.2.1 command line tool on Windows
XP
I've just run some older versions of the command line tool and the
last time
the value 281474976710655 was stored correctly was 3.0.8 I was
missing a
couple of releases after 3.0.8 but saw the unexpected behaviour start
in
3.1.2. Maybe it was introduced in 3.1?
The bug was introduced by check-in [2246] on 2005-Jan-20 just prior
to 3.1.0. Any integer between 140737488355328 and 281474976710655
is stored incorrectly. I'll put in a patch sometime today.
--
D. Richard Hipp <[EMAIL PROTECTED]>
