Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Django 1.3 and South migrations

I have an existing project which extensively uses South migrations to load data into its tables.

Since upgrading to Django 1.3 our unit tests no longer run because they cannot find the data they rely on.

  1. Is this behaviour is due to one of the backwards incompatible changes in 1.3
  2. Is there an easy way for me to convert all these migrations into fixtures?
like image 549
Craig Blaszczyk Avatar asked Jul 05 '11 14:07

Craig Blaszczyk


1 Answers

  1. Yes, this behavior is due to this change.

    There seems to be a workaround in South trunk (see https://bitbucket.org/andrewgodwin/south/changeset/21a635231327 ) so you can try South development version (it is quite stable in my experience).

  2. You may try to change the DB name in settings (in order to get clean environment), run ./manage.py syncdb and ./manage.py migrate and then do ./manage.py dumpdata

like image 102
Mikhail Korobov Avatar answered Sep 19 '22 14:09

Mikhail Korobov