mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-04-06 06:26:41 +00:00
Code Issues 32 Releases Wiki Activity

[3.0.x] Fixed #30955 -- Doc'd that only concrete base models are stored in historical models bases.

Browse Source 
Abstract models are removed from bases when generating historical model
state since 6436f1fad9ce51f18735106ac75aeea3d6d1f310.
Backport of 8058d9d7adb189fec75a4b57565f225996c7b22c from master
This commit is contained in:
Shipeng Feng 2019-11-08 16:41:36 +08:00 committed by Mariusz Felisiak
parent 87a10c3d6e
commit 59578ebaa0
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/topics/migrations.txt
View File

@ -412,11 +412,11 @@ classes will need to be kept around for as long as there is a migration
referencing them. Any :doc:`custom model fields </howto/custom-model-fields>`
will also need to be kept, since these are imported directly by migrations.
In addition, the base classes of the model are stored as pointers, so you must
always keep base classes around for as long as there is a migration that
contains a reference to them. On the plus side, methods and managers from these
base classes inherit normally, so if you absolutely need access to these you
can opt to move them into a superclass.
In addition, the concrete base classes of the model are stored as pointers, so
you must always keep base classes around for as long as there is a migration
that contains a reference to them. On the plus side, methods and managers from
these base classes inherit normally, so if you absolutely need access to these
you can opt to move them into a superclass.
To remove old references, you can :ref:`squash migrations <migration-squashing>`
or, if there aren't many references, copy them into the migration files.