#29777: ORA-00933: SQL command not properly ended with pagination in a
ModelViewSet
-------------------------------------+-------------------------------------
Reporter: zorky | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Normal | Resolution:
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 Carlton Gibson):
Hi...
> After an upgrade from Django 2.0.6 to Django 2.1.1 and DRF 3.8.2...
OK. DRF 3.8.2 supports both Django 2.x and Django 2.1.x. Can you please
downgrade Django (and keep DRF 3.8.2) and verify it works there?
(Then at least the change is presumably in Django, rather than DRF or your
code.)
If so, could you then git bisect to find the change? (See
[https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
tickets/#bisecting-a-regression the guide on using bisect].)
Ideally we need to reduce this down to an issue that only involves Django
itself...
--
Ticket URL: <https://code.djangoproject.com/ticket/29777#comment:1>
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.5b0617101e99330784f0d0435ffa9a90%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
