#29777: ORA-00933: SQL command not properly ended with pagination in a
ModelViewSet
-------------------------------------+-------------------------------------
Reporter: zorky | 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 zorky):
Thanks for your response,
But with Django 2.0.6 , pagination worked fine with the same Oracle server
v 11.2.0 (sorry, in the bug, I wrote v 11.0.2 but it's v 11.2.0.4, I asked
to the DBA), and on this page
https://docs.djangoproject.com/en/2.1/releases/2.0/#dropped-support-for-
oracle-11-2, they write "The end of upstream support for '''Oracle 11.2 is
Dec. 2020'''"
Replying to [comment:2 Simon Charette]:
> I'm afraid this has to do with your Oracle version.
>
> Django 2.0 dropped support for Oracle < 12.1 so I assume it happened to
work for your use case but changes such as #28670 which are relied on by
pagination might have broken it.
>
> https://docs.djangoproject.com/en/2.1/releases/2.0/#dropped-support-for-
oracle-11-2
> https://code.djangoproject.com/wiki/SupportedDatabaseVersions#Oracle
--
Ticket URL: <https://code.djangoproject.com/ticket/29777#comment:4>
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.608a2eec6211b9fa1c052ff32b6d82a2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
