Opened 19 years ago
Last modified 13 days ago
#897 new New feature
Bi-Directional ManyToMany — at Initial Version
Reported by: | anonymous | Owned by: | nobody |
---|---|---|---|
Component: | contrib.admin | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | kmike84@…, carsten.fuchs@…, cmawebsite@…, mmitar@…, Hugo Osvaldo Barrera, Emmanuel Katchy, Shai Berger, Mariusz Felisiak | Triage Stage: | Accepted |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Pull Requests: | |||
Description ¶
Allow amnytomany relationships to be defined both ways
E.G
class ItemType(meta.Model):
name = meta.CharField(maxlength=100)
descritpion = meta.CharField(maxlength=250)
class PropertyType(meta.Model):
name = meta.CharField(maxlength=100)
itemtypes = meta.ManyToManyField(ItemType)
Excellent. When I make a new property type in the admin screens I get a
mutiselect window for item types.
What I want to be able to do however is have this work back the other
way too so that whe I create a new item i can specify what property
types apply.
Thanks
According to the ticket's flags, the next step(s) to move this issue forward are:
- To provide a patch by sending a pull request. Claim the ticket when you start working so that someone else doesn't duplicate effort. Before sending a pull request, review your work against the patch review checklist. Check the "Has patch" flag on the ticket after sending a pull request and include a link to the pull request in the ticket comment when making that update. The usual format is:
[https://github.com/django/django/pull/#### PR]
.