Thank you for the response. Unfortunately, my apache module only performs a single SELECT clause of which WHERE clause can be indexed. What I am wondering is the way to stop calling SQLite each time the module processes an HTTP request (eliminate the FLOCK -> READ -> FUNLOCK done by SQLite). # sorry for my poor English...
From: "Paul Smith" <[EMAIL PROTECTED]> > What I've done here is have a table in the database with a single value > containing the 'update id' in it. Then, I've got SQLite triggers set on > UPDATE, DELETE and INSERT for the main data tables. These triggers > increment the 'update id' whenever the main data tables get updated. My > cache routines check the 'update id' table to decide whether the cached > data is still valid. > > It seems to work OK here (where data is read much more than it is written). > If data was being written frequently, then the trigger could potentially > slow those down too much.
