#23410: Backward migrations change overall state rather than reverting single
migration
-----------------------------+------------------------------------
Reporter: Markush2010 | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | 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):
Replying to [comment:10 Naddiseo]:
> Perhaps it would also be prudent to issue a warning if the migrator
detects that there is potential for data loss?
I don't think it makes sense to try to have the migrations system classify
migrations that way (in the general case, it's impossible -- who knows
what happens inside a `RunSQL` or `RunPython` migration). Adding a flag
that is required for migrating backwards achieves the same benefit with
much less complexity.
--
Ticket URL: <https://code.djangoproject.com/ticket/23410#comment:11>
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/069.37654d0a5e00911866b8a8abebe32b02%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
