On 6/17/2019 8:21 PM, Simon Slavin wrote:
On 18 Jun 2019, at 1:09am, Igor Tandetnik <i...@tandetnik.org> wrote:
A connection doesn't need to check locks on every statement - only when it
tries to spill to disk, most commonly during commit.
I think I understand what you wrote.
So the bit of my program can think that its changes were written to the
database and only later might my program find that they weren't ?
Why would it think that, when it didn't successfully commit the transaction?
Should I have used BEGIN EXCLUSIVE ?
If that's what your application's logic calls for, then yes, sure. This way,
you'll get an error on BEGIN EXCLUSIVE statement. Note that, once BEGIN
EXCLUSIVE succeeds, all readers will be locked out until the write transaction
commits or rolls back, thus reducing the concurrency.
--
Igor Tandetnik
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
