Opened 10 years ago
Closed 10 years ago
#23046 closed New feature (wontfix)
Filtered GenericForeignKeys implementation
| Reported by: | Michał Pasternak | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Hi,
with Django 1.7 (THANK YOU EVERYONE INVOLVED IN IT, IT ROCKS!) it was pretty easy for me to create GenericForeignKey implementation, that allows filtering.
https://github.com/mpasternak/djorm-ext-filtered-contenttypes
It is currently PostgreSQL-only and requires Django 1.7c1
Perhaps with some guidance and mentoring from Django devs, this package could become a part of Django - someday.
Note:
See TracTickets
for help on using tickets.
As you said, perhaps someday. Generally it takes some time for things like this to mature and become de facto standards for common patterns. I'm going to close this ticket for now as it seems a bit premature.
If you are interested in contributing to Django development, you may find the django-core-mentorship list of interest. Thanks!