#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
-----------------------------------+--------------------------------------
Changes (by Natalia Bidart):
* easy: 1 => 0
* resolution: => wontfix
* status: new => closed
* type: Bug => New feature
Comment:
Hello! Thank you for taking the time to create this ticket. To me, this is
more of a feature request than a bug. The current behavior is intentional:
Django always checks for a consistent migration history to protect
projects from entering an invalid state, even when using `--fake`.
The need to bypass this check seems very specific to a niche recovery
scenario rather than something that applies broadly. Django aims to
provide robust, predictable behavior for common cases, so changing this
would fall outside that scope.
Given the above, I'll close the ticket accordingly. If you'd like to
pursue this as a potential feature, please review the
[https://docs.djangoproject.com/en/stable/internals/contributing/bugs-and-
features/#requesting-features feature request guidelines] for more
details.
--
Ticket URL: <https://code.djangoproject.com/ticket/36643#comment:4>
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/01070199ce32baf0-51389f8d-e1ff-462a-bfe3-ee97c8b1a2a7-000000%40eu-central-1.amazonses.com.
