#36938: Unioning an ordered queryset fails on Oracle unless a limit is taken
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: (none)
Type: Bug | Status: new
Component: Database layer | Version: 6.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: oracle, union, | Triage Stage: Accepted
order_by |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Harish Bonu):
* has_patch: 0 => 1
Comment:
Submitted a pull request with a fix to remove unnecessary ORDER BY clauses
from UNION components when compiling subqueries on backends that do not
ignore ORDER BY in subqueries (e.g., Oracle).
CI checks have passed successfully.
PR: https://github.com/django/django/pull/20850
--
Ticket URL: <https://code.djangoproject.com/ticket/36938#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 visit
https://groups.google.com/d/msgid/django-updates/0107019cceb19195-e6475a6d-ab6c-4c35-902d-03338848853c-000000%40eu-central-1.amazonses.com.
