#29630: Oracle crash querying multiple tables with the same column name
"ORA-00918:
column ambiguously defined"
-------------------------------------+-------------------------------------
Reporter: zelfor5436 | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Normal | 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
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* cc: felixx (added)
* component: contrib.admin => Database layer (models, ORM)
* easy: 1 => 0
* type: Uncategorized => Bug
* stage: Unreviewed => Accepted
Comment:
The ''easy picking'' flag is used for
[https://docs.djangoproject.com/en/2.1/internals/contributing/triaging-
tickets/#easy-pickings tickets that would require small, easy, patches].
For example a typo in an error message or something that be performed why
a search and replace through the code base.
Any ORM bug does't fit into this category. The fact it only manifests
itself on Oracle which a most of contributors have limited knowledge of
also makes it harder to resolve.
I've switched the component to the database layer because while it
manifests itself in the admin in your case such an ambigously defined
query can be trivially constructed by using `select_related('fk')` or
`values('id', 'fk__id')`.
@felixx are you aware of any changes that might caused such breakage? At
this point I suspect some obscure flag Oracle flag might be interfering
with native limit/offset support added in #28670 since the test suite
passes against Oracle 12 on CI.
--
Ticket URL: <https://code.djangoproject.com/ticket/29630#comment:7>
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.dd5fcc92b9be51cb41456d5fe25b3268%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
