Re: unexpected sqlite_busy behaviour within transactions

[email protected] Wed, 26 Feb 2020 11:10:22 +0100
Newsgroups gmane.comp.db.sqlite.general
Message-ID <trinity-1fc556c4-2c7a-4189-9bc9-6e3d968e02e4-1582711822060@3c-app-gmx-bs04>
Dear Igor, Andy, Keith

Thank you for your patience to explain. Now very clear to me why it is not worth for the second process to honor the sqlite_busy handler, and instead returns immediately. In retrospect re-reading with your explanations in mind, I also understand the official documentation.

In my case I will use BEGIN IMMEDIATE TRANSACTION to circumvent the issue.

Best regards

Andreas
_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users