Hello SQLite Users, Hello Dr. Hipp, > After the db1 transaction ends, the db2 UPDATE should be able to > complete. In version 2, db2 would have blocked when it tried to > begin the transaction. Version 3 allows db2 to continue future, > but you still cannot have two threads changing the same database > at the same time, so it eventually blocks.
In v2.8x I was using sqlite_busy_timeout to escape this. Unfortunately, it seems that sqlite3_busy_timeout has no effect: it doesn't wait for x milliseconds for the database to become unlocked, but it returns immediately reporting SQLITE_BUSY. What to do ? Regards, George Ionescu
