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 all UPDATEs or INSERTs (including their related SELECTs), Are their possibilities of writer starvation ? And if yes, what is the preferable solution ? (I mean what is the better approach to handle that) Thanks again. Rohit -- View this message in context: http://www.nabble.com/Multiple-SELECTs-%28and-single-SELECT%29-and-TRANSACTION---tf2072083.html#a5737733 Sent from the SQLite forum at Nabble.com.