#27651: System check disallows two ManyToManyField relations on the same model,
one
to concrete through and one to proxy of same through
-------------------------------------+-------------------------------------
Reporter: Tim | Owner: Tim Graham
Graham |
Type: | Status: assigned
Cleanup/optimization |
Component: Core | Version: master
(System checks) |
Severity: Normal | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
The models added in #17002 looks okay but they don't validate with the
errors:
m2m_through_regress.Event.people: (fields.E340) The field's intermediary
table 'm2m_through_regress_individualcompetitor' clashes with the table
name of 'm2m_through_regress.ProxiedIndividualCompetitor'.
m2m_through_regress.Event.special_people: (fields.E340) The field's
intermediary table 'm2m_through_regress_individualcompetitor' clashes with
the table name of 'm2m_through_regress.IndividualCompetitor'.
--
Ticket URL: <https://code.djangoproject.com/ticket/27651>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.140268570b7a0ae7fd76cfc4643e6b54%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
