Smart reversion of Django migrations based on Git diff
Project description
If you are in a complex Django project, sometimes you will find yourself switching between multiple branches, some of which can add a number of database migrations. Before switching back to master you will have to unapply all migrations that are specific to the current branch. To make things worse, in order to unapply Django migrations, you have to enter the migration that comes right before the first migration of the current branch. It’s not that big of a deal, Django is smart enough to let you use an unambiguos prefix of any migration, but with this package you can speed things up a little bit.
While standing on any branch, you can use:
python manage.py unmigrate master
Or if it’s going to be master anyways, this will suffice:
python manage.py unmigrate
And that’s it!
A little deeper
Ok, you can do more than that.
Do you need to unapply your migrations from the same branch, a few commits behind? Here’s how:
python manage.py unmigrate HEAD~5 python manage.py unmigrate af332b python manage.py unmigrate v1.33.7
If you only want to see the target migrations:
python manage.py unmigrate --dry-run
And if you just want to play with this, go ahead and unapply your migrations with fake. Just don’t forget to apply them again:
python manage.py unmigrate --fake python manage.py migrate --fake
Contributing
Join the discussion at https://gitter.im/django-unmigrate/community.
PRs are welcome! If you have questions or comments, please use the link above.
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Hashes for django_unmigrate-0.1.1-py3-none-any.whl
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | 5fa8a33f232e3673d61b90e04ceb40f2624bda21583fe131319abab073c6f3f2 |
|
| MD5 | de18ca7629d415659d542a63bdd73563 |
|
| BLAKE2b-256 | f77c1c57c70288781a8abc3b0d711aa49f598d4a7d0e8911f2512f1d1cae26a9 |
