can continue with 11g by creating django default tables manually?
On Saturday, March 21, 2020 at 11:57:47 PM UTC+6, Simon Charette wrote:
-- On Saturday, March 21, 2020 at 11:57:47 PM UTC+6, Simon Charette wrote:
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
Le samedi 21 mars 2020 12:55:56 UTC-4, Md. Rakibul Islam 131-35-385 a écrit :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??
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/a883b46b-992a-487e-b792-fbaa3252eed4%40googlegroups.com.
No comments:
Post a Comment