#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 akaariai):
I think the problem is that the user never asked for backwards migration.
Having "./manage.py migrate a 0001" unapply dependencies is a dangerous
API. Either add --backwards flag to migrate or at least ask the user if
they want to unapply the dependent migrations.
Also, I think --noinput should *not* assume that the user wants to unapply
dependencies. Unapply should only happen if the user explicitly tells
Django to do so. For this reason the --backwards flag seems better - it is
much harder to unapply migrations accidently, and there is no problem for
--noinput interpretation (what if the user wants to unapply dependencies,
and wants to use --noinput?)
--
Ticket URL: <https://code.djangoproject.com/ticket/23474#comment:10>
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.8f96e2b9ba14a85ebeb851833531b913%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
