Hi Sabine, Thank you! It is really nice getting positive feedback. The migrations section (Part II next week!) is a very basic introduction, aimed at people who have never used South or native migrations. One of the key takeaways (hopefully) of the article is the fact that it is easy to manually edit migrations, and that you are encouraged to do so.
Concerning early development cycles and migration reset, if you are pre-deploy, you currently have three options: - disable migrations entirely during early development (will cease to be possible in Django 1.9; **inadvisable**) - `squashmigrations` once models are ready - delete all migrations and start from scratch once models are ready I would recommend one of last two. The choice really comes down to how your engineering team is set up. If you are in a position where you can get the change to everyone at once, then the third option is viable (but keep a backup!). However, if you have independent developers, this may be dangerous/frustrating, and `squashmigrations` is likely a better option. The `squashmigrations` command is also what you should use in the long term. I do not cover it's use, but you may find the following documentation worthwhile: https://docs.djangoproject.com/en/1.7/topics/migrations/#squashing-migrations Unfortunately, I will not cover the admin in my article. Personally, I prefer the command line, as I am able to mover more quickly than the admin panel. This is completely subjective, of course, and not a criticism of the admin. For testing data, however, you may find data migrations to be useful in some situations, and I advise for their use. Part II will walk through multiple data migrations implementations in both Django 1.6 and Django 1.7. Note that data migrations cannot be automatically squashed. If you use data migrations, this will result in migration file editing down the line. This should not be a problem, but I also don't want that to surprise you. I hope this and future articles are helpful! Thanks again for the positive feedback. Andrew PS I do not mind if you share my article. In fact, I would be delighted if you did. Please do! -- 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/B1553DFD-D9F9-4435-9C78-727E9263B46A%40andrewsforge.com. For more options, visit https://groups.google.com/d/optout.
