is there any way to django3.0 & oracle 11g together?

[Md. Rakibul Islam 131-35-385]

My organization uses Oracle 11g there is no way to upgrade it.

I am facing some issues with oracle 11g & Django 3.0. when i try to migrate a model in django 3.0 i face below mentioned problem:

django.db.migrations.exceptions.MigrationSchemaMissing: Unable to create the django_migrations table (ORA-02000: missing ALWAYS keyword)

To solve it i switched to django 1.11.17 but it is generating below mentioned error.

ImportError: cannot import name 'path' from 'django.urls' (C:\Users\RAKIB\AppData\Local\Programs\Python\Python38\lib\site-packages\django\urls\__init__.py).

is there any solution??

[Simon Charette]

Django 3.0 only supports Oracle 12.2 and and 18c[0].

Django 2.2 only supports Oracle 12.1+[1]

Django 1.11 supports Oracle 11g but LTS support for it will end in April[2].

In short even if you downgrade to 1.11 LTS you won't get any support from Django after less than two weeks.

It looks like Oracle 11g has not been supported since August 2013 [3]

If you can't upgrade your Oracle setup I suggest you consider moving to a different database such as PostgreSQL.

Simon

[0] https://docs.djangoproject.com/en/3.0/releases/3.0/#dropped-support-for-oracle-12-1

[1] https://docs.djangoproject.com/en/2.2/ref/databases/#oracle-notes

[2] https://www.djangoproject.com/download/#supported-versions

[3] https://en.wikipedia.org/wiki/Oracle_Database

[Md. Rakibul Islam 131-35-385]

can continue with 11g by creating django default tables manually?

[Benjamin Daneker]

I just ran into the same issue, my company only recently upgraded to 11g and they won't be upgrading again anytime soon. I've coded in a number of languages over the past several years but I'm still very new to Python, Django, Oracle, and databases in general. Creating the tables by hand is definitely a pain but if doing so would allow me to continue running Django 3.0 I'll happily put in the effort

Obviously the April 2 date has passed so LTS has expired but is there any harm in continuing to use Django 1.11? My app isn't all that complex, just a feedback submission tool, but I don't know what features exist in 3.0 but not in 1.11 that might break the app if I rollback my version.