Christopher R. Palmer wrote:
Unfortunately, that's not the case. The code that was being used when I created ticket 1272 was very simple. In the main thread, I opened a handle for each thread. Each thread then worked independently using only their own handle. This broke the locking because the low-level Linux file locks are tied to the thread that created them. That is, the thread that opened the handle..
So SQLite locks the DB file immediately after opening a connection in sqlite_open?
If all activity on the connection must be restricted to a single thread, how is one to properly use sqlite3_interrupt?
Igor Tandetnik
