Re: [sqlite] Commit fails due to "database is locked" in active transaction

Richard Klein wrote: Requiring the second transaction to complete first is expected in terms of SQLIte's concurrency system. So in terms of using SQLite, I need to close the entire transaction and restart it when I get a "database locked" return code in a writer thread? It's not enough to

Re: [sqlite] Commit fails due to "database is locked" in active transaction

Trevor Talbot wrote: On 1/2/08, Lior Okman <[EMAIL PROTECTED]> wrote: I'm using SQLite3 version 3.4.2 (latest in Debian testing and unstable), and I have a scenario using transactions in SQLite3 that is a bit counter-intuitive. You'll want to look at http://sqlite.org/lockingv

[sqlite] Commit fails due to "database is locked" in active transaction

Hi, I'm using SQLite3 version 3.4.2 (latest in Debian testing and unstable), and I have a scenario using transactions in SQLite3 that is a bit counter-intuitive. I open an SQLite3 database from two terminals. In the first terminal I run the following SQLs: > $ sqlite3 test.db >