Add an extra warning about custom save methods in migrations docs.

1 files changed, 6 insertions, 0 deletions

diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index c585389a14..f8500f2f2d 100644
--- a/docs/topics/migrations.txt
+++ b/docs/topics/migrations.txt
@@ -298,6 +298,12 @@ models will not have any custom methods or managers that you have defined.
 They will, however, have the same fields, relationships and ``Meta`` options
 (also versioned, so they may be different from your current ones).
 
+.. warning::
+
+  This means that you will NOT have custom save() methods called on objects
+  when you access them in migrations, and you will NOT have any custom constructors
+  or instance methods. Plan appropriately!
+
 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