fix(Migrator): prevent nil pointer dereference in AlterColumn#339
Merged
Conversation
When a schema field DBName is absent from ColumnTypes() result (e.g. schema/DB drift, concurrent DROP COLUMN), fieldColumnType remains nil and causes a panic on subsequent method calls. Also propagate the ColumnTypes() error instead of discarding it. Closes go-gorm#338
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
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.
Closes #338
Summary
AlterColumn has two issues:
When schema/DB drift occurs (e.g. concurrent DROP COLUMN, partially applied migration), this causes a nil pointer panic.
Fix
Test Plan