id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 29630,Admin interface causes ORA-00918: column ambiguously defined,zelfor5436,nobody,"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) Configure the use of Oracle as a database 3) Execute makemigrations 4) Execute migrate 5) Execute createsuperuser 6) Execute runserver 7) Open localhost:8000/admin in a browser 8) 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. Interestingly enough, there's no problem when using a SQLite database. 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.",Uncategorized,new,Uncategorized,2.1,Normal,,"oracle, admin, exception",,Unreviewed,0,0,0,0,0,0