Some additional info:

    when the sqlite_lock is returned there is another thread that appears to be 
reading the same table. Does the sqlite3 step return sqlite_locked in this case?

Thanks,
Ken


Ken <[EMAIL PROTECTED]> wrote: 
While using the new 3.5.4 sqlite3_enable_shared_cache I ran into a strange lock 
situation.
    
      SQLITE_LOCK is returned from an insert statement, even though the 
thread/connection performed a successful "begin exclusive" transaction.
     
       begin exclusive
        insert into table...   ---> returns SQLITE_LOCKED

Is it possible for both connections to begin exclusive transactions whilst 
having the shared cache anabled?

Thanks,
ken
 

Reply via email to