#21491 closed Cleanup/optimization (fixed)
Remove outdated workaround in ManyToManyField.related_name documentation
| Reported by: | Baptiste Mispelon | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
There used to be an issue where if you had two M2M fields pointing to the same model, you couldn't use related_name='+' on both.
This was reported in #15932 and fixed by documenting a workaround [1].
However, the underlying issue was fixed in #21375 so I think we can now remove the mention of the workaround.
[1] https://docs.djangoproject.com/en/dev/ref/models/fields/#django.db.models.ManyToManyField.related_name
Change History (3)
comment:1 by , 10 years ago
| Has patch: | set |
|---|
comment:2 by , 10 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I can confirm this fix addressed this specific issue.
PR https://github.com/django/django/pull/1965.