#36938: Unioning an ordered queryset fails on Oracle unless a limit is taken
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Sidharth
| Dusanapudi
Type: Bug | Status: closed
Component: Database layer | Version: 6.0
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: oracle, union, | Triage Stage: Ready for
order_by | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls <jacobtylerwalls@…>):
In [changeset:"6bbe2656e1e89a03d1ae8f2cea7bdd2a027f0665" 6bbe265]:
{{{#!CommitTicketReference repository=""
revision="6bbe2656e1e89a03d1ae8f2cea7bdd2a027f0665"
Refs #36938 -- Reverted "Refs #36938 -- Tolerated unnecessary ordering in
compound queries on SQLite."
This mostly reverts 2314cdf1ff860058a6579bb9f9bac1253fc9ab43,
but keeps the removal of some test skips.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36938#comment:18>
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/0107019e3ce94196-9e5536f5-7e26-4575-94cb-a058a2c6cd35-000000%40eu-central-1.amazonses.com.
