#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 Simon Charette):
> 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.
I believe things are this way because the `migrate` command, with and
without `--fake`, makes graph manipulation expecting the history graph to
be in a consistent state prior to making these changes and that the
operations it performs could venture into undefined behaviour territory
without these per-requisite.
To make a ''typing'' analogy, if a piece of code expect a graph to follow
specific schema (e.g. single head per app, acyclic) and you force it
through the pipe in an unexpected form then it can result in damageable
ways.
Given undefined behaviour is not something we want anywhere close to
database schema alterations I believe the current approach is reasonable.
--
Ticket URL: <https://code.djangoproject.com/ticket/36643#comment:7>
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/01070199e2d22a31-08a08e22-0f2c-43db-acfb-bfd5015eedff-000000%40eu-central-1.amazonses.com.
