#24505: Multiple ManyToManyFields to same "to" model with related_name set to
'+'
mix up badly
-------------------------------------+-------------------------------------
Reporter: gergelypolonkai | Owner:
| marcofucci
Type: Bug | Status: assigned
Component: Database layer | Version: 1.7
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by marcofucci):
I did a bit of research after `jtiai` pointed me in the right direction
and it seems that we've had the same problem before.
To fix the problem, we documented a workaround where `related_name`s had
to be unique, even the ones ending in `+` #15932.
We then thought we had fixed it in #21375 so we deleted the documented
workaround #21491.
Finally, it seems that the bug is back and addressed here.
--
Ticket URL: <https://code.djangoproject.com/ticket/24505#comment:5>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.0e37ad48953ea594f2fcc7ec9d3e7312%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
