Hi, Which version introduced this option?
I am accessing the same connection with multiple threads. I'm seeing a problem since the application locks the database connection during a prepare/step sequence for SELECT operations. It also locks the connection for transactions that perform INSERT/UPDATE operations which effectively serializes database access. This is causing the transactions to be locked out when there are a number of SELECT operations. If I use SQLITE_CONFIG_SERIALZED is it safe to remove the connection lock on my SELECT operations? Will this help my situation or will the lock out just occur in SQLite? FYI, this is using the apr_dbd driver for SQLite3. Thanks, Rick Keiner _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
