Serialization isolation requires 'The databases ends up in the state it
would appear if every transaction were run sequentially'. It doesn't
actually require that all transactions occur sequentially, just that the
database ends up in a state as though they had.
Why do you think that SQLite's
On Tuesday, 9 July, 2019 20:34, Andy Bennett wrote:
>However, the wording for WAL mode is confusing me.
>isolation.html says 'all transactions in SQLite show "serializable"
>isolation.' but it also says 'In WAL mode, SQLite exhibits "snapshot
>isolation"'.
>Snapshot Isolation and Serializable
Hi,
I'm reading the docs:
https://sqlite.org/isolation.html
...and I need some clarification!
It is easy to see that ROLLBACK mode is SERIALIZABLE because all concurrent
readers have to leave before a PENDING lock is upgraded to an EXCLUSIVE
lock.
However, the wording for WAL mode is
Hi,
I want to run the Sqlite tests inside a docker in order to run tests easily on
any platform. Please let me know if you have bad experiences with Docker.
I experience two test cases fail:
sqlite-make-test_1 | ! oserror-1.4.1 expected: [1 {unable to open database
file}]
sqlite-make-test_1
Hi,
I was trying to disable thread safety to get rid of the pthread
dependency with an explicit './configure --disable-threadsafe' on
sqlite-autoconf-328.tar.gz. However, this leads to linker errors:
CCLD libsqlite3.la
CCLD sqlite3
ld:
5 matches
Mail list logo