#29630: Admin interface causes ORA-00918: column ambiguously defined
-------------------------------------+-------------------------------------
Reporter: zelfor5436 | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 2.1
Severity: Normal | Resolution:
Keywords: oracle, admin, | Triage Stage:
exception | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Description changed by zelfor5436:
Old description:
> Attempting to log in to the admin interface causes a SQL exception to be
> raised when using an Oracle database. The exception throw by Oracle is
> ... ORA-00918: column ambiguously defined.
>
> Database: Oracle 12.1
> cx_Oracle version: 6.4.1
>
> Steps to reproduce...
>
> 1) Start a project
> 2) Execute makemigrations
> 3) Execute migrate
> 4) Execute createsuperuser
> 5) Execute runserver
> 6) Open localhost:8000/admin in a browser
> 7) Enter admin username/password and click to log in
>
> At this point, Django will respond with an exception page indicating that
> Oracle has raised a SQL exception. Rolling back to Django 2.0.7
> eliminates the problem and the admin interface behaves as expected.
>
> It looks like the cause is related to base.html used in the admin
> templates. I'm assuming the problem is either related to some kind of
> change, since 2.0.7, in how SQL is constructed, or changes/additions in
> what kind of statements are being emitted by the templates for the admin
> interface.
New description:
Attempting to log in to the admin interface causes a SQL exception to be
raised when using an Oracle database. The exception throw by Oracle is ...
ORA-00918: column ambiguously defined.
Database: Oracle 12.1
cx_Oracle version: 6.4.1
Steps to reproduce...
1) Start a project
2) Execute makemigrations
3) Execute migrate
4) Execute createsuperuser
5) Execute runserver
6) Open localhost:8000/admin in a browser
7) Enter admin username/password and click to log in
At this point, Django will respond with an exception page indicating that
Oracle has raised a SQL exception. Rolling back to Django 2.0.7 eliminates
the problem and the admin interface behaves as expected.
It looks like the cause is related to base.html used in the admin
templates. I'm assuming the problem is either related to some kind of
change, since 2.0.7, in how SQL is constructed, or changes/additions in
what kind of statements are being emitted by the templates for the admin
interface.
I'll try to dig into this further on Monday when I return to work.
Relatively new to Django, so I'm not as familiar as I'd like to be with
what's going on under the hood and I'm not sure where to really begin
digging in as this deals with things that come prepackaged with the
framework.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/29630#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 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.c33da7a4f9d5f19c8e4401e9c40fea9c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
