#35963: Add option to `makemigrations` to skip checking consistent history
--------------------------------+--------------------------------------
Reporter: Curtis Maloney | Owner: (none)
Type: New feature | Status: closed
Component: Migrations | Version: dev
Severity: Normal | Resolution: duplicate
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):
* resolution: => duplicate
* status: new => closed
* type: Uncategorized => New feature
* version: 5.1 => dev
Comment:
Hello Curtis and David, thank you for your proposal and extra rationale.
This feels like a duplicate of #33421 which in turn is an "almost"
duplicate of #31504.
From looking at the code, the consistency check is skipped if the DB is
not available. I'll close as dupe, but please feel free to add further
rationale on either:
1. how this is different from the linked tickets, or
2. whether the solution provided in #31504 is not working for any reason.
--
Ticket URL: <https://code.djangoproject.com/ticket/35963#comment:2>
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/01070193885e70d0-94270145-3a2c-453b-894b-ec440bd450c9-000000%40eu-central-1.amazonses.com.
