Many thanks for helping.
While using SQLite dll Version 3.3.4 on Windows
- Multiple threads/processes access SQLite database,
- Each thread does some SELECTs, INSERTs or UPDATEs.
If for some single SELECT (where user input is used in SQL statement, so to
avoid SQL injection),
It depends upon your application. For it to function optimally you
should make each transaction on your application an SQL transaction,
commit it on success or rollback if there is a problem. In that way you
make each transaction atomic and maintain the integrity of your database.
Since
Thanks for clearing doubt.
Now question is...
While using SQLite dll Version 3.3.4 on Windows
- Multiple threads/processes access SQLite database,
- Each thread does some SELECTs, INSERTs or UPDATEs.
Wrapping all read-only SELECEs with BEGIN TRANSACTION
and using BEGIN EXCLUSIVE to wrap
Hi All,
While using SQLite dll Version 3.3.4 on Windows
- Multiple threads/processes access SQLite database,
- Each thread does some SELECTs, INSERTs or UPDATEs.
Scenario 1
If action of some user needs to execute multiple SELECT statements
(read-only, no plan to write), it needs to start
4 matches
Mail list logo