RohitPatel rohitpatel-/[EMAIL PROTECTED]
wrote:
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
RohitPatel rohitpatel-/[EMAIL PROTECTED]
wrote:
Scenario 1
If action of some user needs to execute multiple SELECT statements
(read-only, no plan to write), it needs to start explicit transaction
to get consistent reads across read-only multiple statements.
Q1. Which one is preferable -
Igor Tandetnik [EMAIL PROTECTED] wrote:
RohitPatel rohitpatel-/[EMAIL PROTECTED]
wrote:
Scenario 1
If action of some user needs to execute multiple SELECT statements
(read-only, no plan to write), it needs to start explicit transaction
to get consistent reads across read-only
Thanks a lot for the answers.
Still I have a doubt (and a question).
Quote from SQLite Document (http://www.sqlite.org/lang_transaction.html)
After a BEGIN IMMEDIATE, you are guaranteed that no other thread or process
will be able to write to the database or do a BEGIN IMMEDIATE or BEGIN
Thanks for the answer and clarification.
BEGIN IMMEDIATE blocks writers, not readers.
I think, BEGIN IMMEDIATE surely blocks writers.
And also blocks new reader(s) if any new reader tries to do BEGIN IMMEDIATE.
Is this correct ?
Ref: Quote from SQLite Document
i Want to Unsubscribe my Account from SQLite
--- Kurt Welgehausen [EMAIL PROTECTED] wrote:
Igor Tandetnik [EMAIL PROTECTED] wrote:
RohitPatel
rohitpatel-/[EMAIL PROTECTED]
wrote:
Scenario 1
If action of some user needs to execute multiple
SELECT statements
(read-only,