*** 36,41 ****
*:: As of check-in [3355] (2006-08-16 after version 3.3.7) this is
now allowed.
! 3: Trying to do two SELECT on the same table at the same time in a multithread application, if sqlite is not set to do so.
!
! (can someone please expand on the 'not set to do so' above?)
--- 36,50 ----
*:: As of check-in [3355] (2006-08-16 after version 3.3.7) this is
now allowed.
! 3: Trying to do two SELECT on the same table at the same time in a
! multithread application, if sqlite is not set to do so.
! _Anonymous adds:_
! can someone please expand on the 'not set to do so' above?
! _DRH replys:_ This third bullet item was added anonymously.
! I am not aware of any restrictions on doing two or more SELECTs
! from different threads at the same time, as long as each SELECT
! is happening in an independent database connection (that is: a
! separate sqlite3* object obtained from separate
! {link: /capi3ref.html#sqlite3_open sqlite3_open()} calls).
! As far as I know, the only time you can get an SQLITE_LOCKED error
! in the latest code is according to the first bullet above.
Small. Fast. Reliable.
Choose any three.
Choose any three.
|
|