#27303: Selecting multiple admin list_filters across relations return results
that
don't match both filters
-------------------------------+------------------------------------
Reporter: Yeago | Owner: nobody
Type: Bug | Status: new
Component: contrib.admin | Version: 1.10
Severity: Normal | Resolution:
Keywords: filterspec | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by steve yeago):
Yeah, with more robust approaches you get both bugs solved and new
features. Perhaps you could elaborate more about what kind of patch you
are hoping to see? One where filterspec objects filter upon objects and
return them, but that somehow doesn't chain ORs? That is fundamentally not
how chained querying works in django. If you're arguing that some kind of
hackery on the filtered queryset to merge the joins is more preferable,
then please say so. I don't really think you understand the parameters of
this problem. If you could help escalate this issue to someone with some
knowledge of the plumbing at play here I would very much appreciate it.
Maybe they could chime in with something useful and we could push this
very crucial and old problem (which I have been contending with for 9
years through maintained forks) forward.
--
Ticket URL: <https://code.djangoproject.com/ticket/27303#comment:34>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.84a3a7c316f8a158e39e6a386c281281%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.