#36643: Migrate should not check for consistent history when faking migrations
-----------------------------------+--------------------------------------
Reporter: Alexandru Chirila | Owner: (none)
Type: New feature | Status: closed
Component: Migrations | Version: 5.2
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Comment (by Natalia Bidart):
After some further research, it's worth mentioning that this seems
somewhat related to #28250, which focused on handling a specific edge case
(--fake-initial) where ignoring the consistency check may be considered
safe.
--
Ticket URL: <https://code.djangoproject.com/ticket/36643#comment:5>
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/01070199ce467d78-a8aa8379-6818-44ff-8cae-5688368906ee-000000%40eu-central-1.amazonses.com.
