#25833: Non-atomic migrations
-----------------------------+------------------------------------
     Reporter:  Pankrat      |                    Owner:  nobody
         Type:  New feature  |                   Status:  new
    Component:  Migrations   |                  Version:  master
     Severity:  Normal       |               Resolution:
     Keywords:               |             Triage Stage:  Accepted
    Has patch:  1            |      Needs documentation:  0
  Needs tests:  0            |  Patch needs improvement:  0
Easy pickings:  0            |                    UI/UX:  0
-----------------------------+------------------------------------

Comment (by hobarrera):

 What happens when a non-atomic migrations fails halfway?
 Your database is no longer in a state matching this migration, nor the
 previous one. The database will be left in an undefined, irrecoverable
 state.

 There's no way to roll back from that either.

--
Ticket URL: <https://code.djangoproject.com/ticket/25833#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.a7812a2afc2a2128282bd141043f9f5f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to