id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
32786	Make the subquery ordering clearing optimization more selectively	Hannes Ljungberg	Hannes Ljungberg	"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."	Cleanup/optimization	closed	Database layer (models, ORM)	dev	Normal	fixed		Simon Charette	Ready for checkin	1	0	0	0	0	0