I have found the problem. There was an incrementing trigger left in
the database accidentally.
----- Original Message -----
From: "John Machin" <sjmac...@lexicon.net>
To: "General Discussion of SQLite Database" <sqlite-users@sqlite.org>
Sent: Sunday, July 12, 2009 4:25 PM
Subject: Re: [sqlite] Number truncation problem in SQLite 3
> On 13/07/2009 8:40 AM, Roger Binns wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Jim Showalter wrote:
>>> create table words (_id integer primary key autoincrement,
>>> wordtext
>>> text not null unique, timestamp integer not null);
>>>
>>> public class Word
>>> {
>>> long _id;
>>> String wordtext;
>>> long timestamp;
>>> }
>>>
>>> timestamp:
>>> before save: 1247435151517
>>> after save : 1247435160847
>
> The "after" number is greater than the "before" number. That's
> truncation? Looks like some more information is required e.g. a
> small
> piece of code (preferably runnable) that shows what exactly was
> done,
> with debug prints in appropriate places.
>
>>>
>>> 64-bit max is: 9223372036854775807, so it should fit.
>>
>> http://catb.org/esr/faqs/smart-questions.html
>>
>> Your mailer headers show that you are using Windows. On Windows
>> (including a 64 bit environment) long is 32 bits.
>
> Ummm, each of the quoted numbers takes up 41 bits (unsigned).
>
> Cheers,
> John
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
