📝 Docs: Schema Migrations with Alembic #899
Open
+207
−0
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
|
📝 Docs preview for commit a58a2c9 at: https://ddde98b2.sqlmodel.pages.dev |
|
FYI: It seems that the Linter is currently throwing errors for the tests in this PR, but this content does not directly involve the SQLModel code itself. |
|
@tiangolo Regarding the proposed roadmap, could you provide more details about your perspective on the direction for integrating migrations through Alembic? |
Csaba1205
approved these changes
Apr 23, 2024
|
📝 Docs preview for commit e8077b9 at: https://8ffce397.sqlmodel.pages.dev |
alejsdev
changed the title
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.
I am aware that this document is still lacking in many aspects. I plan to further utilize the features of mkdocs to improve readability and add supplementary explanations to help users implement the steps appropriately in their respective environments.
Please let me know if there is any additional information that should be included. Going forward, I will actively contribute about the advanced usage of SQLModel in production environments.