#25464: Allow skipping IN clause on prefetch queries
-------------------------------------+-------------------------------------
Reporter: ecederstrand | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by mjtamlyn):
* needs_better_patch: => 0
* stage: Unreviewed => Accepted
* needs_tests: => 1
* needs_docs: => 1
Comment:
Accepting the basic idea here. I'd be interested to see some performance
profiles across a few databases here though, it seems your inner query
there is potentially doing an enormous join to do it's filter, I'm
slightly surprised this is that much more efficient.
Patch needs tests and documentation, and also needs to reassure me what
happens if the prefetched queryset contains extraneous rows. Are they
ignored? Does it throw an error? What should the result be?
--
Ticket URL: <https://code.djangoproject.com/ticket/25464#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 [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/070.6f39f9b9a43c5a262cdb439c7c69aa2a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
