It depends about your workflow - if migrations were applied only on your machine, revert them and modify. South migrations (and Django migrations, which were based on South) may be problematic in speific cases, i.e. during merging or when executed unintentionally from uncleaned *.pyc files, but you're safe until you commit (& spread) changes. And you shouldn't rely on automatic squashing ;)
BR Marcin On Saturday, April 25, 2015 at 2:26:47 PM UTC+2, Timothy W. Cook wrote: > > Django 1.8 Python 3.4 PostgreSQL 9.3 > > During development I am creating several migrations. It seems unnecessary > to keep these since they only exist on my dev machine. > Any data that I have created can be thrown away too. > > Is it safe to delete these migrations (and the database) before deploying > to the next stage for testing by users? > > > -- > > ============================================ > Timothy Cook > LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook > MLHIM http://www.mlhim.org > > -- 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/b32778a9-a5f6-4fe1-931a-93d84037d428%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
