From d36ecbd5306f98231c9f9cbfc78136052fde723a Mon Sep 17 00:00:00 2001 From: David Sanders Date: Wed, 17 Apr 2024 02:11:06 +1000 Subject: [PATCH] [5.0.x] Doc'd that RemoveField also drops related database objects in PostgreSQL. Backport of f0d50a937910571fc4adb7e6fb91045cdc215aa8 from main --- docs/ref/migration-operations.txt | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/ref/migration-operations.txt b/docs/ref/migration-operations.txt index 96a8e4bc8c..3272e1a392 100644 --- a/docs/ref/migration-operations.txt +++ b/docs/ref/migration-operations.txt @@ -197,6 +197,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`` --------------