refactor: update database migration strategy and schema creation #79
Conversation
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
- Modified the `init_db` function to let Alembic handle schema creation, removing the explicit schema creation step. - Updated the `migrate_canvas_data` migration to depend on the new `create_schema` migration, ensuring proper order of operations. - Introduced a new migration file `create_schema.py` to explicitly create the database schema, improving migration reliability.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
init_dbfunction to let Alembic handle schema creation, removing the explicit schema creation step.migrate_canvas_datamigration to depend on the newcreate_schemamigration, ensuring proper order of operations.create_schema.pyto explicitly create the database schema, improving migration reliability.