Conversation
Ensure the DbVersion table contains exactly one row during migrations by using DELETE and INSERT instead of UPDATE. This fixes issues where multiple version rows caused unique constraint failures and rolled back schema migrations. Properly close the database on initialization failure to prevent subsequent operations on a broken state. Initialize new databases with the latest schema version to avoid redundantmigration attempts. Fixes #2105 Signed-off-by: Michael Vetter <jubalh@iodoru.org>
Contributor
|
This fixed the DB issue for me. |
Member
Author
|
I made a mistake in the issue number. This PR fixes #2163. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Ensure the DbVersion table contains exactly one row during migrations by using DELETE and INSERT instead of UPDATE. This fixes issues where multiple version rows caused unique constraint failures and rolled back schema migrations.
Properly close the database on initialization failure to prevent subsequent operations on a broken state.
Initialize new databases with the latest schema version to avoid redundant migration attempts.
Fixes #2105