diff options
| author | Greg Brown <greg@gregbrown.co.nz> | 2014-09-10 09:52:44 +1200 |
|---|---|---|
| committer | Greg Brown <greg@gregbrown.co.nz> | 2014-09-10 09:52:44 +1200 |
| commit | b4d486c80ff6bdfaec8f85e724b44ce5e74a5bb6 (patch) | |
| tree | 84be002be88d72e3f6a49fc50d4afbb93c220c12 | |
| parent | b9d9287f59eb5c33dd8bc81179b4cf197fd54456 (diff) | |
Note re migrations importing custom fields
| -rw-r--r-- | docs/topics/migrations.txt | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt index b1531a54b9..a188ea10c2 100644 --- a/docs/topics/migrations.txt +++ b/docs/topics/migrations.txt @@ -340,7 +340,9 @@ They will, however, have the same fields, relationships and ``Meta`` options 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. +to be kept around for as long as there is a migration referencing them. Any +:doc:`custom model fields </howto/custom-model-fields>` will also need to be +kept, since these are imported directly by migrations. 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 |