#16187: Refactor lookup system
-------------------------------------+-------------------------------------
Reporter: UloPe | Owner: UloPe
Type: | Status: new
Cleanup/optimization | Version: master
Component: Database layer | Resolution:
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 1
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by akaariai):
#10790 just went in, rebased branch available from
https://github.com/akaariai/django/compare/ticket_16187_new
The commit history is ugly... but the basic status is that the above
branch does implement custom lookups in barckwards compatible way. The
next steps would be to convert the GIS ORM to use the custom lookups, and
then to try to implement things like `datefield__year__2000=1`.
After that the big question is how exactly to handle backwards
compatibility. Otherwise I don't see currently any major problems for this
feature.
--
Ticket URL: <https://code.djangoproject.com/ticket/16187#comment:16>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
