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_LOCKEDIs it possible for both connections to begin exclusive transactions whilst having the shared cache anabled? Thanks, ken

