tickets: 16187
This data as json
| id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 16187 | 2011-06-09 13:03:56 | 2017-05-01 04:42:08 | 2022-03-06 04:02:30.755572 | Accepted | closed | Database layer (models, ORM) | Cleanup/optimization | Normal | dev | fixed | Refactor lookup system | There are a few tickets that propose adding new lookup types [1][2][3][4] and also one [5] that suggests adding the possibility for custom fields to have the ability to add their own lookup types. The current implementaion is not able to distinguish between field names and lookup types when querying through a relation. I briefly talked about this topic with Russel, Janis and Alex at the djangocon.eu 2011 sprints. The consensus was that it would be worthwile to do a refactor in this area. It would also allow django to have "awesome fields" as Alex called it :) I'm starting this ticket to track work in this area and also "bundle" the other related tickets. I'll also attach a patch with a basic testcase that fails with the current implementation. [1] #8424 [[BR]] [2] #9596 [[BR]] [3] #10911 [[BR]] [4] #12489 [[BR]] [5] #14263 [[BR]] | akaariai | UloPe | 0 | 1 | 1 | 0 | 0 | 0 |