From 50ae4b4b9e146848ce0d95e76662ec0cf667fbe6 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Sun, 24 Aug 2014 13:33:36 -0400 Subject: [PATCH] Fixed #23131 -- Documented serialization of callable functions in migrations. --- docs/topics/migrations.txt | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt index 9e50a6321f..f08669ac6d 100755 --- a/docs/topics/migrations.txt +++ b/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