#29063: Naming an incompletely applied squashed migration as a migration target
fails with bare NodeNotFoundError
----------------------------+---------------------------------------------
     Reporter:  Julian      |                    Owner:  Jacob Walls
         Type:  Bug         |                   Status:  closed
    Component:  Migrations  |                  Version:  1.9
     Severity:  Normal      |               Resolution:  fixed
     Keywords:              |             Triage Stage:  Ready for checkin
    Has patch:  1           |      Needs documentation:  0
  Needs tests:  0           |  Patch needs improvement:  0
Easy pickings:  0           |                    UI/UX:  0
----------------------------+---------------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"910ecd1b8df7678f45c3d507dde6bcb1faafa243" 910ecd1]:
 {{{
 #!CommitTicketReference repository=""
 revision="910ecd1b8df7678f45c3d507dde6bcb1faafa243"
 Fixed #29063 -- Fixed migrate crash when specifying a name of partially
 applied squashed migrations.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/29063#comment:9>
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.52af2178b9556e4250ce20c3e7460f8d%40djangoproject.com.

Reply via email to