#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:
order_by | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls <jacobtylerwalls@…>):
In [changeset:"cb24bebfab08f55b05599ea1bdcdc159f071225c" cb24beb]:
{{{#!CommitTicketReference repository=""
revision="cb24bebfab08f55b05599ea1bdcdc159f071225c"
Refs #36938 -- Marked a test for union of ordered querysets as an expected
failure on Oracle.
Oracle's SQL parser does not allow ORDER BY in components of a union in
some
cases, so xfail this test until an exception can be raised.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36938#comment:1>
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/0107019c7c384e33-23b33df9-8aa0-4a14-bbb3-8b6c6ae5a374-000000%40eu-central-1.amazonses.com.
