> > South's `--update` also rolled the previous migration back, changed it and > then reapplied it to the current database. >
OK, in that case I can very much see how it's useful for people who develop against a persistent database. That's probably most people. Anyway, the result of this thread for me is that I now consider my original request to be obsolete, as the "git clean" thing is a simple way of getting the behaviour I want for my own style of TDD without hacks. Thanks for your time. Bernie :o) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/8e3ecf3c-aa05-4e3d-b905-3260b093e046%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
