#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):
Replying to [comment:13 Simon Charette]:
> Here's
[https://github.com/django/django/compare/master...charettes:ticket-31255
a branch pushing the idea above further].
After going through this, I have built on top of this and further fixed
the ManyToManyField removal test cases and added another test case for
this ticket as well. How should I create the PR, given that I have built
on top of your existing code.
--
Ticket URL: <https://code.djangoproject.com/ticket/31255#comment:14>
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.a24eb4bb6752163a54d2e940ad106eaf%40djangoproject.com.
