#32786: Make the subquery ordering clearing optimization more selectively
-------------------------------------+-------------------------------------
Reporter: Hannes Ljungberg | Owner: Hannes
Type: | Ljungberg
Cleanup/optimization | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
> So to me this looks like a regression in 3.2.
This behavior was changed in Django 3.0 so per our backporting policy this
means it doesn't qualify for a backport to 3.2.x, even if we consider it a
regression.
See [https://docs.djangoproject.com/en/dev/internals/release-process
/#supported-versions supported versions policy] for more details.
--
Ticket URL: <https://code.djangoproject.com/ticket/32786#comment:10>
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/067.b50e35d91b055b44a3bdfcabb9448842%40djangoproject.com.
