Changes between Version 1 and Version 2 of Ticket #29630


Ignore:
Timestamp:
08/03/18 00:19:48 (4 years ago)
Author:
zelfor5436
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #29630 – Description

    v1 v2  
    77
    881) Start a project
    9 2) Execute makemigrations
    10 3) Execute migrate
    11 4) Execute createsuperuser
    12 5) Execute runserver
    13 6) Open localhost:8000/admin in a browser
    14 7) Enter admin username/password and click to log in
     92) Configure the use of Oracle as a database
     103) Execute makemigrations
     114) Execute migrate
     125) Execute createsuperuser
     136) Execute runserver
     147) Open localhost:8000/admin in a browser
     158) Enter admin username/password and click to log in
    1516
    1617At 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.
     
    1819It 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.
    1920
     21Interestingly enough, there's no problem when using a SQLite database.
     22
    2023I'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.
Back to Top