#32786: Make the subquery ordering clearing optimization more selectively
-------------------------------------+-------------------------------------
Reporter: Hannes | Owner: Hannes Ljungberg
Ljungberg |
Type: | Status: assigned
Cleanup/optimization |
Component: Database | Version: dev
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
This will allow to add support for
[https://code.djangoproject.com/ticket/32776 Array subqueries on
PostgreSQL]. It appears like we would only have to adapt `In.process_rhs`
to do the clearing when the `rhs` value is an instance of `Query` and
fullfils the requirements of clearing the ordering. As
[https://code.djangoproject.com/ticket/32776#comment:1 Simon commented in
#32776] about this we would also want to keep clearing ordering for
`Exists` and and `Queryset.exists()` and since these both end up running
`Query.exists()` which runs `clear_ordering` we should be fine.
I looked around historically and found out that there've been an attempt
at this [https://github.com/django/django/pull/8417 before] but it ended
up being [https://github.com/django/django/pull/8433 reverted] due to some
failures on Oracle. We'll need address these failures if they are still
relevant.
--
Ticket URL: <https://code.djangoproject.com/ticket/32786>
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/052.47aed9b9667352a891907bf8408a0ea6%40djangoproject.com.
