[sqlite] multithreaded app and reload from disk for second db handle? [repost]

[re-repost after initial e-mail was mangled up with HTML/XML tags and second was cut short by webmail client. Let's hope yahoo gets it right.] hi, Just to let you know. I did some more tests regarding the reload from disk and skimmed through the source code. Here a quick description of how

[sqlite] multithreaded app and reload from disk for second db handle? [repost]

[repost after initial e-mail was mangled up with HTML/XML tags] hi, Just to let you know. I did some more tests and skimmed through the source code. Here a quick description of how the reloading from disk works in a multithreaded process: (1) If shared cache is disabled, each call to

[sqlite] multithreaded app and reload from disk for second db handle?

hi, Just to let you know. I did some more tests, skimmed through the source code. Here a quick description of how it works: (1) If shared cache is disabled, each call to sqlite3_open() will result in a db handle with its own btree and page cache. If the page cache is not shared, each db

[sqlite] multithreaded app and reload from disk for second db handle?

hi, Despite the threads-are-evil claim... What happens with respect to the page cache if I have an application (= one multi-threaded process) opening two DB handles (sqlite3_open()) - one DB handle dedicated to one thread. Do multilpe db handles in the same process cause sqlite to reload