Try an EXCLUSIVE TRANSACTION. Dennis Brakhane wrote:
(In case it matters, im running SQLite 3.2.8)Hi. I have a problem with multiple processes that use transactions on the same database: Suppose I have two processes that access the same database Now, both do a "begin transaction", which succeeds Process A now issues "insert into foo values ('bar')", which succeeds Process B now also issues "insert into foo values ('baz')", which fails - database is locked Now, neither can commit the changes. So, at least one has to do a rollback; this however means that I will need to store the data (which is generated on-the-fly during the transaction) somewhere, which seems kinda pointless to me. I'm storing data so that I can store them in a database. So, is there a way to solve this problem?
