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

Merge pull request #3208 from gregplaysguitar/master 

Note re migrations importing custom fields
This commit is contained in:
Andrew Godwin 2014-09-09 16:06:42 -07:00
parent b9d9287f59 b4d486c80f
commit aa4d10d919
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/topics/migrations.txt
View File

@ -340,7 +340,9 @@ They will, however, have the same fields, relationships and ``Meta`` options
References to functions in field options such as ``upload_to`` and References to functions in field options such as ``upload_to`` and
``limit_choices_to`` are serialized in migrations, so the functions will need ``limit_choices_to`` are serialized in migrations, so the functions will need
to be kept around for as long as there is a migration referencing them. 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 just stored as pointers, In addition, the base classes of the model are just stored as pointers,
so you must always keep base classes around for as long as there is a migration so you must always keep base classes around for as long as there is a migration