Fix SwappableDB.Swap to preserve original database on failure #2104
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.
The
SwappableDB.Swap()
function previously deleted the original database files immediately before attempting to open the new database. If the swap operation failed for any reason (e.g., corrupted file, permission issues, invalid SQLite format), the original database was permanently lost.This change implements a safe swap operation that follows atomic principles:
Changes Made
Example of the issue:
Technical Implementation
Test Coverage
Added comprehensive tests:
Test_SwapFailurePreservesOriginal
: Verifies original database remains functional after swap failuresTest_SwapWithWALFiles
: Tests proper handling of WAL files during rollback operationsThe implementation ensures database operations are now safe and atomic - if a swap fails for any reason, the original database files are completely restored and remain fully functional.
Fixes #2103.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.