#36643: Migrate should not check for consistent history when faking migrations
-----------------------------------+--------------------------------------
Reporter: Alexandru Chirila | Owner: (none)
Type: Bug | Status: new
Component: Migrations | Version: 5.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-----------------------------------+--------------------------------------
Comment (by Andrew Williamson):
Hi, I'm struggling to think of the scenario where you'd fake a migration
over an inconsistent history, and it'd leave a consistent state that you'd
not need to fake the next time. I.e. it'd always be inconsistent, every
time. Can you provide an example of where this would help?
--
Ticket URL: <https://code.djangoproject.com/ticket/36643#comment:1>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070199c0402265-b1f3d62e-aa62-4efd-a455-882541e04971-000000%40eu-central-1.amazonses.com.
