p31829507
/
django
mirror of https://github.com/django/django.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fixed #24650 -- Documented how to change an unmanaged model to managed.

This commit is contained in:
Tim Graham 2016-08-23 17:35:42 -04:00 committed by GitHub
parent fb951fb0c5
commit 80c03b06ad
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/howto/writing-migrations.txt
View File

@ -322,3 +322,12 @@ Also consider what you want to happen when the migration is unapplied. You
could either do nothing (as in the example above) or remove some or all of the could either do nothing (as in the example above) or remove some or all of the
data from the new application. Adjust the second argument of the data from the new application. Adjust the second argument of the
:mod:`~django.db.migrations.operations.RunPython` operation accordingly. :mod:`~django.db.migrations.operations.RunPython` operation accordingly.
Changing an unmanaged model to managed
======================================
If you want to change an unmanaged model (:attr:`managed=False
<django.db.models.Options.managed>`) to managed, you must remove
``managed=False`` and generate a migration before making other schema-related
changes to the model, since schema changes that appear in the migration that
contains the operation to change ``Meta.managed`` may not be applied.