Browse files

Fixed #23131 -- Documented serialization of callable functions in mig…

  • Loading branch information...
1 parent e39af5e commit 50ae4b4b9e146848ce0d95e76662ec0cf667fbe6 @timgraham timgraham committed Aug 24, 2014
Showing with 4 additions and 0 deletions.
  1. +4 −0 docs/topics/migrations.txt
@@ -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

0 comments on commit 50ae4b4

Please sign in to comment.