On 25 Feb 2013, at 10:22pm, Greg Janée <gja...@ucop.edu> wrote: > I'm accessing an SQLite database from two processes simultaneously. If > there's contention, one process will receive an SQLITE_BUSY; that's fine. > However, occasionally a process will receive an SQLITE_IOERR with the > extended result code SQLITE_IOERR_LOCK.
Have you set a SQLite timeout of a few seconds ? See here: <http://www.sqlite.org/c3ref/busy_timeout.html> > I was expecting to get SQLITE_BUSY and nothing else. If the _BUSY state lasts for longer than the timeout you've set, then you'll get _IOERR. Setting a long timeout gives the software longer to deal with the busy condition quietly before concluding that something has locked up the databases longer than reasonable. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
