#23474: Schema migrations can inadvertently destroy data
---------------------------------+------------------------------------
Reporter: Naddiseo | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.7
Severity: Release blocker | Resolution: fixed
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 Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"d7ab2cefb7ec94bf45d37a02c79b6703ea2880e5"]:
{{{
#!CommitTicketReference repository=""
revision="d7ab2cefb7ec94bf45d37a02c79b6703ea2880e5"
Revert "Fixed #23474 -- Prevented migrating backwards from unapplying the
wrong migrations."
This reverts commit abcf28a07695a45cb5fb15b81bffc97bea5e0be3.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23474#comment:14>
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/066.aa050463a68fb9abf5dba468961badda%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
