KUSHAL SHAH <adroi...@yahoo.com> wrote: > My scenario: Multiple processes want to access the database. How do I > configure so that I can get as much concurrency w.r.t read > and write. Meaning, have multiple readers and writers.
The best concurrency between separate processes (and thus, necessarily, separate connections) you can achieve with SQLite is by enabling WAL mode. Which, as I said, gives you multiple readers and a single writer at the same time. Under no circumstances would SQLite allow two simultaneous writing transactions. > That is fine, I can handle it in my application. However, I just want to > confirm, how to achieve the multi-read and 1 write > scenario. My understanding: > Keep threading mode to Serialized. If you don't have multiple threads sharing a single connection (and it sounds like you don't), then threading mode is irrelevant. > Keep the locking mode to Normal. Again, this is the default. So I don't have > to do anything. > Finally, the journal mode to WAL. > > Is this correct? Yes, sounds good to me. -- Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
