#24505: Multiple ManyToManyFields to same "to" model with related_name set to
'+'
mix up badly
-------------------------------------+-------------------------------------
Reporter: gergelypolonkai | Owner:
| marcofucci
Type: Bug | Status: closed
Component: Database layer | Version: 1.7
(models, ORM) |
Severity: Normal | Resolution: fixed
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 Tim Graham <timograham@…>):
In [changeset:"0e2d3b93043676975aa921a70b5faafef02cac5c" 0e2d3b9]:
{{{
#!CommitTicketReference repository=""
revision="0e2d3b93043676975aa921a70b5faafef02cac5c"
[1.8.x] Fixed #24505 -- Fixed clash with hidden m2m fields.
Added support for multiple m2m fields with the same 'to' model
and with related_name set to '+'.
Backport of 4ee08958f154594b538207a53c1d457687b3f7ae from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24505#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 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.0609be82e553fefbef01106041c84a9d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
