Opened 3 years ago
Closed 3 years ago
#33557 closed New feature (needsinfo)
Traversing a reverse Generic Foreign Key
| Reported by: | rymanso | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 4.0 |
| Severity: | Normal | Keywords: | QuerySet.extra |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Traversing a reverse Generic Foreign Key.
When we initially designed our system we created a model with a Generic Foreign Key as opposed to Generic Relations on all models.
As Django doesn't support traversing a reverse generic foreign key relationship, we can do so using an "extra" query.
If discontinued we will have to make larger changes to our system.
Change History (1)
comment:1 by , 3 years ago
| Component: | Uncategorized → Database layer (models, ORM) |
|---|---|
| Resolution: | → needsinfo |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Thanks for the ticket, however reverse generic relations can be handled with
GenericRelation(). I'm not sure what exact feature you are requesting.Please follow triaging guidelines with regards to new features and describe clearly and concisely what the missing feature is.