On Sat, Oct 10, 2009 at 07:38:08PM +0100, Simon Slavin scratched on the wall: > > On 10 Oct 2009, at 7:04pm, Roger Binns wrote: > > > Ron Arts wrote: > >> So I am wondering if I can drop the glib Hash Tables, and > >> go sqlite all the way. But I'm afraid the process of > >> constructing SQL queries / parsing them by sqlite, and > >> interpreting the results in my app, multiple times per > >> event will be too slow. > > Don't forget to use transactions, even for when you are just doing > SELECTs without changing any data.
Using transactions speeds up a long series of SELECTs because it eliminates the need to re-acquire a read-only file-lock for each individual SELECT. Since in-memory databases have no file locks, I'm not sure that is relevant to this specific case. -j -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Our opponent is an alien starship packed with atomic bombs. We have a protractor." "I'll go home and see if I can scrounge up a ruler and a piece of string." --from Anathem by Neal Stephenson _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
