#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 Naddiseo):
My understanding of the PR was that it stopped the unapplication of
migrations that weren't applied to begin with; rolling back a no-op should
still be a no-op.
The issue I was facing was that m.0001 is already applied (and along with
it some other that it depends on) then I try to migrate it again. Since
it's already applied, the operation shouldn't touch the database, but
instead it rolls back its dependencies.
Perhaps @andrewgodwin can shed some light on this since he wrote it -> is
the outcome of the use case I provided in my second comment the expected
behaviour?
--
Ticket URL: <https://code.djangoproject.com/ticket/23474#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 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.5a5c47faf3aae1649c904716c1ac45d6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
