On Sep 30, 2008, at 11:39 AM, Rick Keiner wrote: > 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? >
SQLITE_CONFIG_SERIALIZED has been the default behavior since version 3.5.0. All it does is move the locks to inside of SQLite so that your application code does not have to mess with them. It does not magically provide you any additional concurrency. D. Richard Hipp [EMAIL PROTECTED] _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
