#23410: Backward migrations change overall state rather than reverting single
migration
-----------------------------+------------------------------------
Reporter: Markush2010 | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Changes (by aaugustin):
* type: Bug => New feature
* stage: Unreviewed => Accepted
Comment:
Yes, let's accept the ticket according to Carl's suggestion in comment 4.
A convention such as `migrate appname -0002` to migrate to just before
migration 0002 might work.
--
Ticket URL: <https://code.djangoproject.com/ticket/23410#comment:8>
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/069.45d8a1e2609ae1a3d17538deef9760d6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
