Comments on: SQLite again http://blog.xcski.com/2006/01/31/sqlite-again Everything I used to bore people on newsgroups and mailing lists with, now in one inconvenient place. Fri, 22 Aug 2008 00:16:30 +0000 http://wordpress.org/?v=2.6.1 By: Joe D http://blog.xcski.com/2006/01/31/sqlite-again#comment-1613 Joe D Tue, 31 Jan 2006 12:23:35 +0000 http://xcski.com/blogs/pt/2006/01/31/sqlite-again#comment-1613 I found out about SQLite a year or so ago, and have been keeping it in mind should I ever have a project that needs it. So while I haven't used it, I've been reading up on it. The FAQ at sqlite.org says that it locks the whole database file whenever anything needs to update it, which is what you're seeing. It's 6:30AM, so I'm a little fuzzy and probably haven't thought things through. You could try is to cache the results somewhere. Generate a hash from the parameters, and then use that as the key, or something. I don't know how many duplicates you generate, so it may not save you anything. You'd obviously have to clear the cache on a database reload. You could also create a temporary database for each generation, populate it, and then delete it when it's done. I found out about SQLite a year or so ago, and have been keeping it in mind should I ever have a project that needs it. So while I haven’t used it, I’ve been reading up on it. The FAQ at sqlite.org says that it locks the whole database file whenever anything needs to update it, which is what you’re seeing.

It’s 6:30AM, so I’m a little fuzzy and probably haven’t thought things through.

You could try is to cache the results somewhere. Generate a hash from the parameters, and then use that as the key, or something. I don’t know how many duplicates you generate, so it may not save you anything. You’d obviously have to clear the cache on a database reload.

You could also create a temporary database for each generation, populate it, and then delete it when it’s done.

]]>