This repository was archived by the owner on Sep 6, 2024. It is now read-only.
Fix running table altering migrations #68
Merged
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
04b3aef to
7682038
Compare
|
Would you mind also rebasing and then re-creating the initial migration? |
7682038 to
a5c1990
Compare
Paillat-dev
approved these changes
Jul 27, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Since SQLite doesn't support the
ALTER TABLEcommand, running migrations that alter the structure of database tables with alembic fails. To fix this, alembic provides a render_as_batch option, which will instead create new tables, copy the data over from the old ones and then remove the old ones, bypassing this limitation.