Opened 8 years ago
Last modified 8 years ago
#27651 closed Cleanup/optimization
System check disallows two ManyToManyField relations on the same model, one to concrete through and one to proxy of same through — at Initial Version
| Reported by: | Tim Graham | Owned by: | Tim Graham |
|---|---|---|---|
| Component: | Core (System checks) | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
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'.
Note:
See TracTickets
for help on using tickets.