#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 Markush2010): With the patch [abcf28a076] being applied I cannot rollback to a previous migration if. Furthermore the detection of the "next_migration" is wrong and depends on a leading number in the migration name which is not required. Dependencies are defined explicitly and not implicit by their name. -- Ticket URL: <https://code.djangoproject.com/ticket/23474#comment:12> 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 django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/066.a097a5c042485d7f617a80ef79fe2f7d%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.