I have no experience with SQLite other than for testing it on Glorp and using it in Android (that provides a locking mechanism to queue requests), but according to the documentation it depends on how the SQLite connection is opened, if it is opened in "Serialized" mode [1], then it is safe to have a multi threaded application operating on a single db file. Also, according to the docs the access is controlled by means of file locking [2], so if everything is finalized/closed properly you shouldn't have this issue.
Regards! [1] https://www.sqlite.org/threadsafe.html [2] https://www.sqlite.org/howtocorrupt.html Esteban A. Maringolo 2016-07-12 6:20 GMT-03:00 Alistair Grant <akgrant0...@gmail.com>: > > On 12/07/2016 10:19 AM, "Hilaire" <hila...@drgeo.eu> wrote: >> >> Hi, >> >> So what is it exactly regarding busy state of Sqlite? >> The documentation is very short, to not say inexistant, on that specific >> important matter. > > I also haven't read anything official, but my experience is that if the db > is locked sqlite waits a while. If the db unlocks, the transaction succeeds, > if not, an error is returned. > > Cheers, > Alistair
