#23474: Schema migrations can inadvertently destroy data
---------------------------------+------------------------------------
Reporter: Naddiseo | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by carljm):
After discussion with MarkusH and looking at the patch here more closely,
I agree with him that this particular implementation is problematic and
should be rolled back.
I still favor a change in behavior as described in my comment above, but
it needs a better implementation. That discussion can happen on the
mailing list and/or #23410.
--
Ticket URL: <https://code.djangoproject.com/ticket/23474#comment:13>
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.142f91522eb4173f4df6ab35f9a03601%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
