The key factor here is not the total time taken to perform these operations but the fact that the time is *increasing* for each run. I am looking for consistency in that I need to be able to let the application perform these steps in constant time over a long period of time (months).
Dropping the table is not an option since I always will have some data in the table (even though I delete everything in my test). Maybe the culprit is that I delete everything from the table? JP -----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Matthew L. Creech Sent: 16. júní 2009 15:51 To: kon...@payplus.com; General Discussion of SQLite Database Subject: Re: [sqlite] Database inserts gradually slowing down On Tue, Jun 16, 2009 at 11:31 AM, Konrad J Hambrick<kon...@payplus.com> wrote: > > Hmmm ... > > Is there a way to replace step 5 (delete everything from the table) > with a System-Level rm / unlink and a sqlite CREATE TABLE ? > This shouldn't be necessary unless the table has triggers. From http://sqlite.org/lang_delete.html : "When the WHERE is omitted from a DELETE statement and the table being deleted has no triggers, SQLite uses an optimization to erase the entire table content without having to visit each row of the table individual. This "truncate" optimization makes the delete run much faster." -- Matthew L. Creech _______________________________________________ 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
