#31255: Migrations create a redundant RemoveField operation when deleting 2
models
with related fields.
-------------------------------------+-------------------------------------
Reporter: Panagis | Owner: Rohit Jha
Alisandratos |
Type: | Status: assigned
Cleanup/optimization |
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: migration,optimizer | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Sanskar Jaiswal):
Forgive me if I come off as a bit unaware, I have just started to work
with the migrations component. I have been going through the code in the
meanwhile, and I am confident that the `reduce()` method or
`MigrationOptimizer`'s `optimize_inner()` method is causing the issue.
Just to be on the same page, the issue here is that while one
`RemoveField` gets reduced into `DeleteModel`, while the other does not,
right?
--
Ticket URL: <https://code.djangoproject.com/ticket/31255#comment:11>
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/066.552c414aa639c61c0f05bbed7b0c0d07%40djangoproject.com.
