Add --migration-table-name flag to migrate command#152
Open
knwoop wants to merge 1 commit intocloudspannerecosystem:masterfrom
Open
Add --migration-table-name flag to migrate command#152knwoop wants to merge 1 commit intocloudspannerecosystem:masterfrom
knwoop wants to merge 1 commit intocloudspannerecosystem:masterfrom
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
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.
WHAT
Add
--migration-table-namepersistent flag to themigratecommand that allows users to specify a custom migration tracking table name.--migration-table-name(default:SchemaMigrations)up,version,setWHY
This enables running multiple migration systems in a single database. For example:
SchemaMigrations(default)OperationalMigrations(custom)This is useful for teams that want to separate DDL schema changes from DML data migrations while using the same tool.