I should have been more specific. There are lots of threads, Identifying which thread is having the lock at any given time would have been helpful.
Also need clarification on this one - A reader thread should still be able to read data from database until writer thread in transaction tries to commit the data? On Thursday, 13 March 2014 4:43 PM, Simon Slavin <slav...@bigfraud.org> wrote: On 13 Mar 2014, at 11:12pm, veeresh kumar <veeru...@yahoo.com> wrote: > Thanks a lot for the response. Is there any way to identify which > thread/process is actually blocking the reader thread or vise versa? Only in that it's the one that didn't get the error message. The one that's in the middle of a SQLite API call. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
