Opened 13 years ago
Closed 10 years ago
#14263 closed New feature (duplicate)
Allow fields to support custom double-underscore lookup methods
| Reported by: | Carl Meyer | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | jonas-django@…, ojiidotch@… | Triage Stage: | Accepted |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Rather than continually adding specialized builtin lookup types (e.g. #2616), there should be a good way for custom field types to support their own custom lookup types. Currently this is sort of possible, but requires monkeypatching the global singleton registry of lookup types, which is not ok.
Change History (7)
comment:1 Changed 13 years ago by
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 Changed 12 years ago by
| Severity: | → Normal |
|---|---|
| Type: | → New feature |
comment:3 Changed 12 years ago by
| Easy pickings: | unset |
|---|---|
| UI/UX: | unset |
Related: #16187 Refactor of the lookup system
comment:4 Changed 12 years ago by
| Cc: | jonas-django@… added |
|---|
comment:5 Changed 12 years ago by
| Cc: | ojiidotch@… added |
|---|
comment:6 Changed 11 years ago by
I believe this is related: https://code.djangoproject.com/ticket/6439
Note: See
TracTickets for help on using
tickets.
Marking accepted per design discussion with core devs (Russell, Malcolm, Jannis) at sprint.