fix(migrations): remove hard-coded bigint types for postgres#8934
Open
bujjibabukatta wants to merge 1 commit into
Open
fix(migrations): remove hard-coded bigint types for postgres#8934bujjibabukatta wants to merge 1 commit into
bujjibabukatta wants to merge 1 commit into
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.
Fixes #8867.
Updated the Testmo and Q Dev scope_config_id migrations to avoid hard-coded BIGINT SQL type declarations in GORM tags. The migrations continue using migrationhelper.AutoMigrateTables, but now allow GORM to generate dialect-compatible column definitions for both MySQL and PostgreSQL.
Validated with git diff --check and targeted searches for the previous BIGINT UNSIGNED/raw ALTER TABLE patterns.