Closed
Conversation
Collaborator
|
Tested with both sqlite and postgres, working fine |
nmveeresh
reviewed
Dec 11, 2025
Collaborator
nmveeresh
left a comment
There was a problem hiding this comment.
Tested with both sqlite and postgres, working fine.
nmveeresh
approved these changes
Dec 11, 2025
Collaborator
nmveeresh
left a comment
There was a problem hiding this comment.
Tested with both sqlite and postgres, working fine..
ad8515b to
d588947
Compare
6c1836b to
d588947
Compare
Signed-off-by: Madhav Kandukuri <madhav165@gmail.com>
Signed-off-by: Madhav Kandukuri <madhav165@gmail.com>
Signed-off-by: Madhav Kandukuri <madhav165@gmail.com>
Member
|
Closed in #1584 |
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
5 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.
This pull request enhances the Alembic migration to support multiple database backends (PostgreSQL, SQLite, and MySQL) by dynamically handling constraint naming and accommodating database-specific behaviors such as type casting and constraint renaming. Both the upgrade and downgrade paths have been improved to ensure safer and more robust migrations across all supported databas