summaryrefslogtreecommitdiff
path: root/docs/topics/migrations.txt
diff options
context:
space:
mode:
authorJacob Walls <jacobtylerwalls@gmail.com>2021-12-24 18:37:22 -0500
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2022-01-21 17:10:31 +0100
commit2d8232fa716f5fe46eec9f35a0e90c2d0f126279 (patch)
tree1b600a3c218b92db5077ede96ea86ca574b8a428 /docs/topics/migrations.txt
parenteeff1787b0aa23016e4844c0f537d5093a95a356 (diff)
downloaddjango-2d8232fa716f5fe46eec9f35a0e90c2d0f126279.tar.gz
Fixed #26760 -- Added --prune option to migrate command.
Diffstat (limited to 'docs/topics/migrations.txt')
-rw-r--r--docs/topics/migrations.txt7
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index d7daa69281..73dec300e0 100644
--- a/docs/topics/migrations.txt
+++ b/docs/topics/migrations.txt
@@ -715,6 +715,13 @@ You must then transition the squashed migration to a normal migration by:
Once you've squashed a migration, you should not then re-squash that squashed
migration until you have fully transitioned it to a normal migration.
+.. admonition:: Pruning references to deleted migrations
+
+ .. versionadded:: 4.1
+
+ If it is likely that you may reuse the name of a deleted migration in the
+ future, you should remove references to it from Django’s migrations table
+ with the :option:`migrate --prune` option.
.. _migration-serializing: