#16187: Refactor lookup system
-------------------------------------+-------------------------------------
Reporter: UloPe | Owner: UloPe
Type: | Status: new
Cleanup/optimization | Version: 1.3
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 julien):
akaariai, I agree that it'd be nice to avoid multiple traversals of the
lookup query and that, to do so, some big-ish refactoring would be
required. In the meantime, I have posted a patch (with tests) in #11670
with a slightly simpler algorithm than the ones originally posted here and
there. That patch aims to fix the possible collisions between genuine
field names and built-in lookup types.
I'm not sure whether that bug should be fixed in priority or if it should
wait for the general refactoring to happen.
--
Ticket URL: <https://code.djangoproject.com/ticket/16187#comment:9>
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 this group at
http://groups.google.com/group/django-updates?hl=en.
