99% of the time, the cost of an action involving a database call is in the database. Especially, if you're using DBD::SQLite for anything more than a toy. DBD::SQLite is, frankly, less than optimizable. The biggest problem is how the columns are compared, especially dates.
I would look at DBM::Deep over DBD::SQLite. I guarantee you'll notice a large speedup if you're at least halfway decent.
- In general, if you think something isn't in Perl, try it out, because it usually is. :-)
- "What is the sound of Perl? Is it not the sound of a wall that people have stopped banging their heads against?"