From 5dc4a8652cd6e2a80fbedd8984f30c8fc482c3ea Mon Sep 17 00:00:00 2001 From: Andrew Godwin Date: Tue, 28 Jan 2014 14:10:40 +0000 Subject: [PATCH] Add an extra warning about custom save methods in migrations docs. --- docs/topics/migrations.txt | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt index c585389a14d..f8500f2f2dd 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