Hi RIchard, any chance this BEGIN CONCURRENT branch will make it into a
next SQLite standard release?
On 2019/01/19 3:07 PM, Richard Hipp wrote:
If you are daring, you can also try building from the begin-concurrent
branch (https://www.sqlite.org/src/timeline?r=begin-concurrent) and
using "BEGIN CONCURRENT" instead of "BEGIN" to start your transaction.
In that case, the COMMIT might still fail with a conflict, but only if
the intervening transaction modified pages of the database file that
your transaction actually read. So if the database has two tables,
and you are updating one table, and some other process is updating the
other table, then there is a high chance that both transaction will
run to completion.
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
