#29630: Oracle crash querying multiple tables with the same column name when
limit/offset is used.
-------------------------------------+-------------------------------------
Reporter: zelfor5436 | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: oracle, admin, | Triage Stage: Accepted
exception |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jani Tiainen):
According to Oracle docs 12.1 (se2) premier support ended on July 2018,
and extended one ends on july 2021.
> To ensure database security and minimize Oracle support costs,
organizations should plan to upgrade 11.2.0.4 and 12.1.0.2 databases in
2018 and move to 12.2 at that time. All new databases should be 12.1.0.2
and look to begin production use of 12.2 in late 2017 or with the release
of 12.2.0.2 in early 2018.
One option could be to use old rownum based OFFSET..LIMIT for Oracle 12.1
if that wouldn't require much of the changes to backend rather than trying
to fix unique column names.
--
Ticket URL: <https://code.djangoproject.com/ticket/29630#comment:16>
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.55c24ba324ea4b76af3ddc25d196d0cd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
