Keith Medcalf wrote > See also Write Ahead Logging journal mode (WAL) where in the case you > specified B's operation will succeed even if it is updating a table being > read by connection A.
Oh, good to know! For anyone who stumbles across this thread in the future, note that this requires that you be using separate private caches between connections A and B. With a shared cache, you still get SQLITE_LOCKED even with write-ahead logging. -- 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
