> Will sqlite3_unlock_notify() work for this, or do I need to be > doing something else?
No, sqlite3_unlock_notify() doesn't work for multi-process applications. For them you should do some retries after delay by yourself (probably using sqlite3_busy_handler() ) or use sqlite3_busy_timeout(). Pavel On Thu, Sep 17, 2009 at 1:04 PM, Angus March <an...@uducat.com> wrote: > I was under the impression that when a C API function attempts to get a > lock on the db that it cannot get, it blocks until it can get the lock. > Well it turns out that this isn't true. > Googling for 'sqlite locking block' has directed me to > http://www.sqlite.org/unlock_notify.html, which suggest that I should be > using the sqlite3_unlock_notify() function. However, it also states that > this is for multi-threaded applications. My project is a multi-/process/ > one. Will sqlite3_unlock_notify() work for this, or do I need to be > doing something else? > If someone has a better solution, I'd love to hear it, and soon, > because I'm in crunch time. > _______________________________________________ > 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
