#28315: Support an API for filtering of GenericForeignKeys
-------------------------------------+-------------------------------------
Reporter: Michał Pasternak | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: generic foreign | Triage Stage:
keys content types filtering | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* has_patch: 1 => 0
* resolution: => duplicate
Comment:
Duplicate of #23046. Hi again, three years later. ;-)
Perhaps you can raise the idea on the DevelopersMailingList to get some
other feedback. I think many developers avoid `GenericForeignKey` in the
first place so I'm not if enhancing the functionality is a big priority. I
noticed several "this is a hack" comments in your project. I would say you
should either try to clean those up before moving forward, or explain how
inclusion in Django will allow removing the hacks.
--
Ticket URL: <https://code.djangoproject.com/ticket/28315#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.3a7500f2be8fd65b39b78ac4b6119298%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
