Re: [Django] #34866: Cannot inspect migrations that replace squashed migrations with sqlmigrate

[Django]

#34866: Cannot inspect migrations that replace squashed migrations with sqlmigrate
----------------------------------+---------------------------------------
Reporter: Giovanni Allegri | Owner: Pal-Sandeep
Type: Uncategorized | Status: assigned
Component: Migrations | Version: 4.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
----------------------------------+---------------------------------------
Changes (by Pal-Sandeep):

* owner: nobody => Pal-Sandeep
* status: new => assigned

--
Ticket URL: <https://code.djangoproject.com/ticket/34866#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#34866: Cannot inspect migrations that replace squashed migrations with sqlmigrate
----------------------------------+---------------------------------------

Reporter: Giovanni Allegri | Owner: Sandeep Pal
Type: Bug | Status: closed
Component: Migrations | Version: 4.2
Severity: Normal | Resolution: needsinfo

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 Mariusz Felisiak):

* cc: David Wobrock (added)
* status: assigned => closed
* resolution: => needsinfo
* easy: 1 => 0
* type: Uncategorized => Bug

Comment:

> However, in case the squashed migrations remove a model or a field, the
command breaks when it reaches the migration that replaces the squashed
migrations. since this will try to modify a model that was already removed
(by the squashed migrations).

I cannot reproduce any crash in such a scenario. Please reopen the ticket
if you can debug your issue and provide a sample project that reproduces
the issue.

--
Ticket URL: <https://code.djangoproject.com/ticket/34866#comment:4>