Hi Jesse, Yes, in certain cases, native Django migrations may run very slowly.
https://code.djangoproject.com/ticket/22608 My understanding is that this should not be a problem unless you have a huge number of apps and models (note how the second benchmark from Paul in the ticket has 200 models). If migrations are running very slowly for you, I would recommend sticking with Django 1.6 and using South first. The upgrade strategy at this point should be: - upgrade your dependencies to the latest versions (Python, third party apps, etc) - ensure that the dependencies work with Django 1.7 (Python 2.7, Python 3.2+, etc) - Attempt upgrade - test (and fix) - test again - do migrations run super slowly? Revert to Django 1.6 and South, wait for Django 1.7.1 (expected fix). Quick heads up: `syncdb` is deprecated in Django 1.7. If you're using Django 1.7, you should first call `makemigrations`, verify the contents of the file, and then call `migrate` to build/alter the database. However, despite deprecation, `syncdb` should not be having an effect on your migration speeds. Hope that helps, Andrew -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/94FCA249-0BDB-4300-B203-C201A6CE2BE5%40andrewsforge.com. For more options, visit https://groups.google.com/d/optout.
