#35677: Unexpected behaviour of Prefetch with queryset filtering on a through
model
-------------------------------------+-------------------------------------
Reporter: David Glenck | Owner: (none)
Type: Uncategorized | Status: closed
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: Prefetch, | Triage Stage:
prefetch_related, many-to-many | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* resolution: => needsinfo
* status: new => closed
Comment:
Hello David, thank you for the detailed report and the models and
reproduction steps you provided. I’m having trouble understanding the
specific behavior you’re reporting that seems inconsistent with the
documentation you referenced.
If the issue you’re encountering is related to the documented behavior of
spanning multi-valued relationships, it might be a duplicate of issues
such as #29196, #29271, #16554, or others. If the issue is different,
could you please provide a brief summary or rephrase what you believe the
bug in Django is?
--
Ticket URL: <https://code.djangoproject.com/ticket/35677#comment:1>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701914d954b2b-263c2e40-91a8-4cf8-9156-bf253a21655a-000000%40eu-central-1.amazonses.com.
