Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SQLite unlock notify is not handled for BEGIN statements #2021

Closed
madadam opened this issue Aug 4, 2022 · 1 comment · Fixed by #2055
Closed

SQLite unlock notify is not handled for BEGIN statements #2021

madadam opened this issue Aug 4, 2022 · 1 comment · Fixed by #2055

Comments

@madadam
Copy link
Contributor

madadam commented Aug 4, 2022

unlock notification was implemented in #1658 but only when calling sqlite3_step. The BEGIN statement is executed using sqlite3_exec and the unlock notification is not handle there. This means that one can still get SQLITE_LOCKED_SHAREDCACHE errors when running multiple transactions concurrently.

The fix I think is to do something like this also here.

I'm happy to contribute a PR to fix this.

@abonander
Copy link
Collaborator

Please do!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants