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.
What gave you this impression in the first place? If this were true, what would be the purpose of sqlite3_busy_handler and sqlite3_busy_timeout? > 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. Are you using shared cache mode? > However, it also > states that this is for multi-threaded applications. My project is a > multi-/process/ one. Then you are not using shared cache mode, and the article doesn't apply to you in any way. > Will sqlite3_unlock_notify() work for this No > or do I need to be doing something else? Yes. Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
