#29630: Oracle crash querying multiple tables with the same column name when
limit/offset is used.
-------------------------------------+-------------------------------------
Reporter: zelfor5436 | Owner: felixxm
Type: Bug | Status: closed
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: oracle, admin, | Triage Stage: Accepted
exception |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"5aeced6dcd881dfe7413da5356be0e9f14da3d40" 5aeced6d]:
{{{
#!CommitTicketReference repository=""
revision="5aeced6dcd881dfe7413da5356be0e9f14da3d40"
[2.1.x] Fixed #29630 -- Fixed crash of sliced queries with multiple
columns with the same name on Oracle 12.1.
Regression in 0899d583bdb140910698d00d17f5f1abc8774b07.
Thanks Tim Graham for the review and Jani Tiainen for help.
Backport of 024abe5b82d95ee60cb18a77ebf841ad715467fa from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29630#comment:22>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.156bd0215ebc290265dfc3a93f21c772%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
