#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):
I've updated the patch to avoid some test failures with foreign keys by
adding the following special case:
{{{#!python
if len(part) > 3 and part[-3:] == '_id'
field, _, _, _ = model._meta.get_field_by_name(part[:-3])
...
}}}
That feels a bit hacky but it works.
I'd really like to push this over the line for 1.4 as it's causing several
issues in the ORM and the admin. So I'm wondering: What is the roadmap for
this? How could the current patch be improved? What API is considered to
make the lookups configurable?
I'm a total noob in regards to the ORM codebase but I'm keen to help out
under some supervision :)
--
Ticket URL: <https://code.djangoproject.com/ticket/16187#comment:5>
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.
