> My reading of the code has the readers flushing their cache often, and > not > using the journal at all to maintain consistency. My reading has the > reader start with nothing in the cache, lock the database with a read > lock, perform as many SQL queries as are in the single text string it's > currently parsing, and flush its cache around the time it unlocks the > database.
So if the cache is thrown away after every transaction, does that mean that if I do "select * from mytable" twice in a row (in different transactions), that there will be the same number of read() system calls for the second one? Even if there are no intervening changes? That hardly seems optimal, even within the constraints of the sqlite architecture..... -mda --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
