#27155: makemigrations --no-check-consistency command line argument
-------------------------+-------------------------------------------------
Reporter: | Owner: nobody
sjoerdjob |
Type: | Status: new
Uncategorized |
Component: | Version: 1.10
Migrations | Keywords: makemigrations,
Severity: Normal | check_consistent_history
Triage Stage: | Has patch: 0
Unreviewed |
Easy pickings: 0 | UI/UX: 0
-------------------------+-------------------------------------------------
There are a number of edge-cases for makemigrations where it fails in 1.10
while it did not fail in 1.9.
To quote Tim Graham in #27142:
> I'm beginning to think that makemigrations shouldn't have this check in
the first place due to the many issues that have been reported (#27054,
#27110, #27141) and the more and more complexity that seems needed to add
to fix it. Other opinions welcome. In my view, the most natural thing to
do after creating a migration is to apply it, so it doesn't seem like
delaying the check from makemigrations to migrate would have a huge
drawback.
I propose that we add a command line argument `--no-check-consistent-
history` (or something similar, bikeshed away!) which skips the calls to
`check_consistent_history`.
To me it seems like this should be possible to add in the next release and
takes the pressure off fixing the corner-cases a bit to make sure we can
come up with a good solution.
--
Ticket URL: <https://code.djangoproject.com/ticket/27155>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.cd52ed211f4b72d00a8c29b34b2db258%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
