The first case is definitely a source of friction for me too. Django
management commands could help but it's still up to the developer to
remember to run them. I'd prefer to have the VCS identify and help resolve
these situations right when they arise.
The second case seems to be discouraged b
See if this solves part of the problem
https://github.com/lorinkoz/django-unmigrate
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an
I run into the problem you're trying to solve often and it's quite
frustrating. I don't think storing the migration text in the database is
the right solution - I don't know why, but it just *feels* wrong.
Such a rollback would only support SQL based migrations - any RunPython
migration operati
