SQLite Forum

lock and low concurrency
hi everybody, i'm reading the book <inside sqlite> that publish in April 15, 2007.in the book ,it says: "the sqlite lock is database file oriented.so if any one transaction is writing to any part of a database file, all other transactions are prevented from reading or writing any part of the file."

in most common case,one transaction want to read/write table_1 and another transaction read or write table_2.

anyone knows does sqlite support table-oriented lock in new version?

if sqlite doesn't support table-oriented lock ,how to improve the performance in case transaction operate in different table?

in my simple idea, make an agreement at application level: 1 database-file only contains 1 table,so the lock in different tables is lock in different database file.the concurrency performance is better. anyone knows method to improve the performance ?