Opened 12 years ago
Closed 12 years ago
#18621 closed Cleanup/optimization (duplicate)
Two ManyToMany fields without backwards relation
Reported by: | anonymous | Owned by: | anonymous |
---|---|---|---|
Component: | Documentation | Version: | 1.4 |
Severity: | Normal | Keywords: | backwards relation model |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
I tried to use two ManyToMany fields without allowing a backwards relation on the same model.
I couldn't make it work successfully so i asked about it on StackOverflow, then they thought it may be a bug in django. so i'm posting the issue right here.
http://stackoverflow.com/questions/11382801/two-manytomany-fields-without-backwards-relation
Change History (4)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:3 by , 12 years ago
Component: | Database layer (models, ORM) → Documentation |
---|---|
Triage Stage: | Unreviewed → Accepted |
Type: | Bug → Cleanup/optimization |
comment:4 by , 12 years ago
Resolution: | → duplicate |
---|---|
Status: | assigned → closed |
Actually a duplicate of #15932.
Note:
See TracTickets
for help on using tickets.
Set
related_name='foo+'
on one field andrelated_name='bar+'
on the other. It will work.The documentation could explain that.
That said, Frank's comment isn't wrong:
To be honest, I'm not sure why this feature exists!