> Doesn't enabling WAL mode address the transaction size limit?
Yes, you are right. WAL mode will eliminate transaction size issue,
although there will be a WAL-file size issue. ;) But that issue is
only about disk space, nothing related to locking of reading
transactions.
Pavel
On Fri, Jun 17
* Pavel Ivanov:
> To answer your original question: if you disable shared cache, start
> reading transaction on one connection and start writing transaction on
> the other connection then you'll be able to read on the first
> connection database in the state it was before writing transaction.
> Bu
> Hmm... unless read_uncommited is persistant somehow; looks like if I
> just don't try to use shared cache it works... I thought I had
> disabled cache before alone and still got the same results...
read_uncommitted works only when shared_cache is on.
To answer your original question: if you dis
If I disable enable_shared_cache then there is a pragme
read_uncommitted that doesn't generate the locks; so non shared,
read_uncommited combination works;
I tried 'PRAGMA journal_mode=WAL' which says it returns a string; I
assume that if I treat it as a query and sqlite3_step I should get
back t
4 matches
Mail list logo
