#33759: Using subquery to filter a model delete generates a sub-optimal SQL
-------------------------------------+-------------------------------------
Reporter: Christofer Bertonha | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Mariusz I think that it makes sense to only enable the query wrapping when
necessary through a feature flag as you've suggested.
As for the MySQL limited subquery issue that's a different can of worms.
The unnecessary query wrapping should be testable on backends with the
feature disabled by counting the number of `SELECT`.
Thanks for the ping and sorry for my late answer!
--
Ticket URL: <https://code.djangoproject.com/ticket/33759#comment:6>
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/010701817ec11811-736f2bb7-073b-40cc-9db9-a1f0fbb5979b-000000%40eu-central-1.amazonses.com.
