#34791: Prefetch's queryset attribute is ignored when the same nested relation
is
used multiple times.
-------------------------------------+-------------------------------------
Reporter: Maxime Toussaint | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: prefetch, | Triage Stage: Accepted
prefetch_related |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Maxime Toussaint):
So, it makes sense that the order matters, especially for Prefetch with
to_attr, since until it has been fetched, it does not exist yet. Here
though, these are 2 very separate calls to the database that have
absolutely no interaction with each other. Shouldn't they be independent?
It doesn't make sense to me that it works in one order but it does not in
the other. I am vey surprised to hear that such a thing could be the
intended behaviour, as I can't make sense of why it could be. If you could
give more depth to your reasoning, it would be much appreciated.
--
Ticket URL: <https://code.djangoproject.com/ticket/34791#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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018a27a70a7c-34a4f96f-766c-42fc-9b9e-f68686d20a27-000000%40eu-central-1.amazonses.com.
