Igor, thanks. I almost always use BEGIN IMMEDIATE, so I missed the BEGIN [DEFERRED] variant. Guess it solves the problem, though it seems the lock won't be acquired before SELECT happens.
Best regards, Igor -----Original Message----- From: Igor Tandetnik [mailto:[EMAIL PROTECTED] Sent: Monday, November 19, 2007 3:26 AM To: SQLite Subject: [sqlite] Re: Any way to obtain explicit read lock? Igor Sereda <[EMAIL PROTECTED]> wrote: > Suppose we need to read two tables in an isolated way, so no db change > is visible to the connection between first and second readout. > As far as I see, there's no such SQL or API for that at the moment. Just do both SELECT's within a single transaction. See BEGIN, COMMIT Igor Tandetnik ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] ----------------------------------------------------------------------------- ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
