#24535: Make "manage.py migrate" atomic, i.e. rolling back any migrations on
failure
-----------------------------+--------------------
Reporter: blueyed | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------
While each migration by itself appears to be atomic, the whole "manage.py
migrate" process isn't.
I think that it would be useful to wrap it into a transaction altogether.
This would rollback all successful migrations in case a later one fails,
and would help with deployment, where you want to have all or none of the
migrations being applied.
--
Ticket URL: <https://code.djangoproject.com/ticket/24535>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.50d6e9606d993c6252c1af343284075d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
