>> inserted into the database in ascending order, and where there may be as
>> many as 500 hID entries for each timestamp. After a while, this table
> Have you considered making timestamp a PRIMARY KEY?
>
> So, declare it as INTEGER PRIMARY KEY NOT NULL
Unfortunately, the timestamps aren't unique, so I can't use
PRIMARY KEY to solve the problem. (Each run generates as many as 500
entries, all with the same timestamp)
A simple example of the data in the table follows:
<...>
1167615600|111|7|39
1167615600|155|2|8
1167615600|157|4|7
1167615600|220|4|47
1167615600|247|7|21
1167615600|261|8|30
1167615600|308|9|20
<snip>
1167611400|89|7|34
1167611400|101|5|4
1167611400|147|9|14
1167611400|173|7|2
1167611400|195|8|1
1167611400|314|8|12
1167611400|347|6|48
1167611400|364|1|49
<...>
Chris
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
