I've been reading about the shared cache feature and I have a question. It seems to me that there are two ways we can have multiple threads all accessing a database via a "single" connection. One, establish a single serialized private cache connection up front, and give it to all the threads. Two, have each thread independently establish a multi-thread shared cache connection. What are the trade-offs between these two approaches? (I am using "serialized" and "multi-thread" as they are defined here: https://www.sqlite.org/threadsafe.html)
Also, if my application only establishes a single connection to a particular database, does it matter at all if that connection uses a shared or private cache? In particular, I am establishing a single multi-thread connection that I protect with my own mutex. My assumption is "no", but I just want to confirm. -- Sent from: http://sqlite.1065341.n5.nabble.com/ _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
