#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 David Sanders):
I just want to chime in here that I think we ought to consider this
option.
Squashing migrations either through the command or manually using the
replacements process is notoriously unreliable (a patch was submitted
recently to address false circular errors and there's another issue I've
encountered that blocks this).
This leaves developers to brute force squash by simply deleting &
regenerating migrations. I was hoping that `--fake` would work but am
being blocked by `InconsistentMigrationHistory`.
The only option left was to wipe out the migrations table then fake. This
was easy for me to do because I have access but I just wonder whether this
would be a step too far for some folks.
--
Ticket URL: <https://code.djangoproject.com/ticket/36643#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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019abee0afa3-ac05ef3f-e53a-46ba-bcd0-85010a7cb03c-000000%40eu-central-1.amazonses.com.
