If you're using the same database connection they will not progress simultaneously, you need one connection per thread for that to work.
-Jeff On Fri, May 16, 2008 at 8:00 AM, Jeffrey Rennie <[EMAIL PROTECTED]> wrote: > I looked in the documentation, and scanned the source code, but haven't yet > been able to answer this question for myself: > > If two threads are simultaneously trying to execute READ transactions on a > shared sqlite*, will they both progress simultaneously? Or will it be one > after the other? In other words, is there a simple mutex in the sqlite* or > a read/write lock? > > Sincerely, > Jeffrey Rennie > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users