Doc'd that PostgreSQL specifies CASCADE when dropping columns. #18066
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
shangxiao
force-pushed
the
clarify-drop-cascade
branch
from
f047897
to
23ea73b
Compare
nessita
reviewed
Apr 15, 2024
…field in a migration.
nessita
force-pushed
the
clarify-drop-cascade
branch
from
23ea73b
to
fe6e8a3
Compare
nessita
approved these changes
Apr 16, 2024
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.
Submitting an admonition for a gotcha that a colleague spent some time on – they had some views go missing and were wondering what caused it.
I understand that CASCADE may be based on the fact that PG will abort any ALTER TABLE … DROP COLUMN statement if there are any objects dependent on that column 👍 Though probably not a bad idea to just clarify that here. (We could also adjust the wording to say this?)