Skip to content

Doc'd that PostgreSQL specifies CASCADE when dropping columns. #18066

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 16, 2024
Merged

Doc'd that PostgreSQL specifies CASCADE when dropping columns. #18066

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/ref/migration-operations.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -195,6 +195,16 @@ if the field is nullable or if it has a default value that can be used to
populate the recreated column. If the field is not nullable and does not have a
default value, the operation is irreversible.

.. admonition:: PostgreSQL

``RemoveField`` will also delete any additional database objects that are
related to the removed field (like views, for example). This is because the
resulting ``DROP COLUMN`` statement will include the ``CASCADE`` clause to
ensure `dependent objects outside the table are also dropped`_.

.. _dependent objects outside the table are also dropped: https://www.postgresql.org/docs/current/sql-altertable.html#SQL-ALTERTABLE-PARMS-CASCADE


``AlterField``
--------------

Expand Down