#23410: Backward migrations change overall state rather than reverting single
migration
-----------------------------+--------------------------------------
     Reporter:  Markush2010  |                    Owner:  nobody
         Type:  Bug          |                   Status:  closed
    Component:  Migrations   |                  Version:  1.7
     Severity:  Normal       |               Resolution:  invalid
     Keywords:               |             Triage Stage:  Unreviewed
    Has patch:  0            |      Needs documentation:  0
  Needs tests:  0            |  Patch needs improvement:  0
Easy pickings:  0            |                    UI/UX:  0
-----------------------------+--------------------------------------
Changes (by andrewgodwin):

 * status:  new => closed
 * resolution:   => invalid
 * severity:  Release blocker => Normal


Comment:

 The test is exactly correct; the contract is that backwards migrations
 roll back to just after the application of the named migration, and all
 its dependencies are unapplied.

 The problem here is the way we specify nodes on the graph - the choice of
 the same namespace and format as forwards migrations is unfortunate, and
 perhaps instead we should have backwards migrations go to *before* the
 named migration rather than afterward (so you're asking to end up with the
 one you named unapplied) - we'd need to have an alternate syntax for this
 now, though, since we've shipped something as it is.

 I'm going to close this as INVALID, as it's performing exactly as designed
 (though unfortunately different to South). I wouldn't be averse to a new
 ticket for better docs or perhaps even a second input argument format for
 "before this migration" rather than "just after", it's the sort of thing
 that would work well for a sprint.

--
Ticket URL: <https://code.djangoproject.com/ticket/23410#comment:3>
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.c3b8d4d5c2f0d65574e248628418ce3e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to