Repository navigation
Fix migrations - #572
Merged
Merged
Fix migrations#572
Conversation
|
Remember to describe your changes in the changelog! |
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
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.
Fix attribute error in
0044that was causing the optimize capacity attribute to not be migrated properly and typo in0039that was failing on backwards migration (class is calledElectrolyzer)These migrations will have to be applied to a fresh restore of the database, as reversing the migrations currently deletes the storages without restoring them in the old structure. This could theoretically be implemented in the backwards migration. Currently the migration reverses okay, but the storage data is lost.