#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 <felisiak.mariusz@…>):
In [changeset:"c48b34e26d0fd2f445d54d191bfe32d58dfb8e7b" c48b34e]:
{{{
#!CommitTicketReference repository=""
revision="c48b34e26d0fd2f445d54d191bfe32d58dfb8e7b"
Refs #32786 -- Made query clear ordering when ordered combined queryset is
used in subquery on Oracle.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32786#comment:13>
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/01070181a364f2aa-85fd68a0-63fe-400e-a235-74173485a7af-000000%40eu-central-1.amazonses.com.
