#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 Simon Charette):
Here's
[https://github.com/django/django/compare/master...charettes:ticket-31255
a branch pushing the idea above further].
It currently has two failures related to many-to-many field removals
optimizations in the auto-detector but the additional tests in
`test_optimizer` demonstrate that changes work as expected. We should
likely add more tests for the `RemoveField` and `DeleteModel` without
fields(s) tests but I think this should be a good basis if you want to
familiarize yourself with the internals of the optimizer.
--
Ticket URL: <https://code.djangoproject.com/ticket/31255#comment:13>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.3a8de435151a168c3bae278e731e1355%40djangoproject.com.
