Database Suspension #668
Merged
Database Suspension #668
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is because this would allow a database modification to run in an aborted transaction
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request completes #660, defines the notion of suspended databases, and supersedes #663 which is on hold.
A suspended database prevents database locks in order to avoid the
0xdead10ccexception. Basically, all accesses to a suspended database throw an error, but reads in WAL mode.To suspend or resume a database:
Configuration.observesSuspensionNotificationsflag when you create a database queue or pool.Database.suspendNotificationandDatabase.resumeNotification.The content of this pull request is 🔥 EXPERIMENTAL.