On Tue, Jun 22, 2010 at 04:16:42PM -0400, Eric Smith scratched on the wall: > Jim Wilcoxson wrote: > > > Insert times should be constant for the 2nd case: no primary key, no > > indexes; ie, it doesn't matter how many records are already in the > > database. I confirmed this with SQLite 3.6.18. > > Definitely not constant. Looks linear to me -- you saw the plot, you > can decide for yourself.
What OS/filesystem are you using? SQL inserts should be near-constant, assuming the table does not have an INTEGER PRIMARY KEY with explicit values. The table's root B-Tree needs to re-balance every now and then, but if the inserts are in-order (which they will be with an automatic ROWID) this should be rare and cheap-- should should get more rare as the number of rows increases. Many *filesystems* do not provide linear access times, however, especially with larger files. -j -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Intelligence is like underwear: it is important that you have it, but showing it to the wrong people has the tendency to make them feel uncomfortable." -- Angela Johnson _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
