Ticket here: http://www.sqlite.org/cvstrac/tktview?tn=1212 Patch here: http://www.sqlite.org/cvstrac/chngview?cn=2445 Quote from DRH to the mailing list: 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. [and in a later message] I do not have a schedule for the release of the next version of SQLite. Please stick the patch into portage. (Marked critical because it causes data loss.) Reproducible: Always Steps to Reproduce:
Thanks! Fixed in cvs (3.2.1-r2).
