#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 Alexandru Chirila):
Replying to [comment:4 Natalia Bidart]:
> 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`.
I'm not sure I understand, if the consistency check is in place to prevent
**entering** an invalid state, why is it being run **before** the
migration runs? Wouldn't it make sense to run it **after** the migration
is run (but before commit)? Or alternatively it should check consistency
in a "dry run" mode, to compute the state of the dependency graph after
the the migrate runs. Either of these would cover my case as well, and
make the consistency check actually useful.
Because as it stands the consistency checks, does not in fact prevent
entering an invalid state. The only thing it achieves is blocking using
the migrate script if you are already in an invalid state.
--
Ticket URL: <https://code.djangoproject.com/ticket/36643#comment:6>
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/01070199e2be743a-dd7604ac-f519-4514-aa3e-5f30f9e85bb3-000000%40eu-central-1.amazonses.com.
