#29777: ORA-00933: SQL command not properly ended with pagination in a
ModelViewSet
-------------------------------------+-------------------------------------
Reporter: DUVAL Olivier | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
orm,oracle,pagination | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by DUVAL Olivier):
Ok thanks, I understand. I'm going downgrade Django to 2.0.6 and wait for
Oracle v 12 version upgrade in my organization in October / November.
Replying to [comment:6 Simon Charette]:
> @zorky,
>
> The release note I pointed to mentions that ''Django 2.0 officially
supports Oracle 12.1+'' which means that only Django 1.11 LTS, which is
supported until April 2020, officially support Oracle 11.2. Even if the
set of features your application was relying on was working fine on Django
2.0 doesn't mean it officially supported your version of Oracle.
--
Ticket URL: <https://code.djangoproject.com/ticket/29777#comment:7>
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/063.21cd954d49e2ae0a861cf0b1eed80840%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
