sql: check FK back-references in ALTER COLUMN TYPE #71718
Closed
+15
−2
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
Previously, ALTER TABLE ... ALTER COLUMN ... TYPE ... statements would execute regardless if the column is also the target of a foreign key constraint on another table. This commit fixes this bug. Fixes cockroachdb#71709. Release note (bug fix): fixes a bug in which an ALTER TABLE ... ALTER COLUMN ... TYPE ... statement could execute despite the column being the target of a foreign key constraint on another table.
|
This change is |
|
This is wrong. |
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.
Previously, ALTER TABLE ... ALTER COLUMN ... TYPE ... statements would
execute regardless if the column is also the target of a foreign key
constraint on another table. This commit fixes this bug.
Fixes #71709.
Release note (bug fix): fixes a bug in which an ALTER TABLE ... ALTER
COLUMN ... TYPE ... statement could execute despite the column being the
target of a foreign key constraint on another table.