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

Fixed #23131 -- Documented serialization of callable functions in migrations.

This commit is contained in:
Tim Graham 2014-08-24 13:33:36 -04:00
parent e39af5ea59
commit 50ae4b4b9e
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/topics/migrations.txt
View File

@ -331,6 +331,10 @@ They will, however, have the same fields, relationships and ``Meta`` options
when you access them in migrations, and you will NOT have any custom
constructors or instance methods. Plan appropriately!
References to functions in field options such as ``upload_to`` and
``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.
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
that contains a reference to them. On the plus side, methods and managers