Browse files

Add docs about converting from South

  • Loading branch information...
1 parent 05d36dc commit b8c82419455587843df95c01bd9555eaab094854 @andrewgodwin andrewgodwin committed Jan 23, 2014
Showing with 19 additions and 0 deletions.
  1. +19 −0 docs/topics/migrations.txt
19 docs/topics/migrations.txt
@@ -356,3 +356,22 @@ available at the top level of a module it is not serializable.
Django will write out the value as an instatiation of your class with the
given arguments, similar to the way it writes out references to Django fields.
+Upgrading from South
+If you already have pre-existing migrations created with
+`South 0.x <>`_, then the upgrade process to use
+``django.db.migrations`` is quite simple:
+* Ensure all installs are fully up-to-date with their migrations
+* Delete all your (numbered) migration files, but not the directory or - make sure you remove the ``.pyc`` files too.
+* Run ``python makemigrations``. Django should see the empty migration directories and make new initial migrations in the new format.
+* Run ``python migrate``. Django will see that the tables for the initial migrations already exist and mark them as applied without running them.
+That's it! The only complication is if you have a circular dependency loop
+of foreign keys; in this case, ``makemigrations`` might make more than one
+initial migration, and you'll need to mark them all as applied using::
+ python migrate --fake yourappnamehere

0 comments on commit b8c8241

Please sign in to comment.