Hi. I am heaving small problem with sqlite. I have a webapp which connects to the database using sqlite-jdbc and performs SELECTs to response to different GET requests, while this happens if I try to write to a database ( UPDATE or INSERT ) from command line, that (i.e. update process) would occasionally fail with error message "SQL error near line 1: database is locked". Notice that I have only one writer, but many readers. Reading documentation (http://www.sqlite.org/lockingv3.html) I was under impression that process which intends to update database will place it in the pending state allowing all currently running reads ( SELECTs ) to proceed, while blocking new SELECTs, the lock database apply changes and then unlock it allowing all pending and new SELECTs to proceed. Am I right about it and if so why do I "SQL error near line 1: database is locked" when trying to write to a database?
-- Dmitri Priimak _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
