#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
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"024abe5b82d95ee60cb18a77ebf841ad715467fa" 024abe5]:
{{{
#!CommitTicketReference repository=""
revision="024abe5b82d95ee60cb18a77ebf841ad715467fa"
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.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29630#comment:21>
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.b99ab334e14890bb4aaa409e865c177f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
