#36507: Document that only the base queryset’s prefetch_related() is preserved
when
using union()
-------------------------------------+-------------------------------------
Reporter: Clifford Gama | Owner: Chris M
Type: | Status: assigned
Cleanup/optimization |
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: prefetch_related, | Triage Stage: Accepted
union |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Chris M):
* has_patch: 0 => 1
* owner: Clifford Gama => Chris M
Comment:
I have made an attempt at documenting this behavior in this
[https://github.com/django/django/pull/19929 PR].
I'm open to thoughts on how to improve this documentation: if it should
exist somewhere else or if any changes are needed. It is a pretty nuanced
topic, and I was trying to balance covering the details without making it
too confusing.
I included an example of using `Q` objects to filter within the first
`prefetch_related`. However, I'm not sure this is all that helpful of an
example to provide. It feels like it introduces a bit too much complexity
to the documentation.
--
Ticket URL: <https://code.djangoproject.com/ticket/36507#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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070199c1fc0758-87ed0084-03a0-4ca2-812d-64f31a283d7f-000000%40eu-central-1.amazonses.com.
