#34247: Cannot resolve operation dependencies
----------------------------+--------------------------------------
Reporter: Mike Schem | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 4.1
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Comment (by Mike Schem):
Replying to [comment:1 Tim Graham]:
> You'll need to provide a minimal example to reproduce the issue so we
can better understand it. The patch also requires a regression test based
on that.
Yea, I've tried to come up with something, but no luck so far. I've only
been able to get this to fail on my project, and like I said, it has
hundreds of objects with complex relations. The code does fix the problem
and I see no downside to ordering proxy model and model creates at the top
before the sort, any reason not to just accept the PR?
Not sure if I'll be able to come up with something here.
--
Ticket URL: <https://code.djangoproject.com/ticket/34247#comment:3>
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/010701859cce83fb-c68c44e1-5848-44bc-b6a8-a79ecda397c5-000000%40eu-central-1.amazonses.com.
