#15804: Query lookup types should be scoped to the last joined field's model
-------------------------------------+-------------------------------------
Reporter: adrian | Owner: mtredinnick
Type: Bug | Status: new
Milestone: | Component: Database layer
Version: 1.3 | (models, ORM)
Resolution: | Severity: Normal
Triage Stage: Accepted | Keywords:
Needs documentation: 0 | Has patch: 0
Patch needs improvement: 0 | Needs tests: 0
UI/UX: 0 | Easy pickings: 0
-------------------------------------+-------------------------------------
Changes (by mtredinnick):
* owner: nobody => mtredinnick
* ui_ux: => 0
* easy: => 0
* stage: Design decision needed => Accepted
Comment:
This is pretty much related to the fact that all things linking to GIS
models require a GeoManager for just this reason. In my head, it's not
amazingly hard to do this and has been a "should get around to that" item
for quite a while. We would effectively promote the manager to the correct
subclass (which drags in the right QuerySet subclass) as we proceed down
the chain. Particularly in the GIS case, this makes things a *lot* easier.
In practice, it may be a little fiddly, but I don't think it requires
enormous amounts of internal refactoring. Roughly speaking, an attribute
on the manager to say if it needs to be "promoted to" should we enter that
class and awareness of that attribute by various clone methods.
--
Ticket URL: <https://code.djangoproject.com/ticket/15804#comment:2>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
