#33734: InconsistentMigrationHistory triggers on squashed migrations when not
all
replaced migrations are applied
-------------------------------------+-------------------------------------
Reporter: GwynBleidD | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 3.2
Severity: Normal | Resolution:
Keywords: migrations squash | Triage Stage:
inconsistentmigrationhistory | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Thanks for the report. Can you provide a sample project? Can you reproduce
`InconsistentMigrationHistory` in the Django 4.0, 4.1a1, and the current
`main` branch? (we made some improvements in this area.)
--
Ticket URL: <https://code.djangoproject.com/ticket/33734#comment:1>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/01070180f04ce639-0d90ad68-1a2c-4af6-bd50-4f385396bf36-000000%40eu-central-1.amazonses.com.
