The model we use for SQLITE is to use a connection pool (connections opened via sqlite3_open_v2).
We have many threads, but only one thread can use a connection at a time - a thread takes it out of the pool, and when done, returns it to the pool. The only exception to this is calls to: sqlite3_interrupt(), which can be called from any thread. Under that model, do we need to pass SQLITE_CONFIG_MULTITHREAD ? - Deon _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
