#23147: Sliced for-update queries do not work on Oracle
-------------------------------------+-------------------------------------
Reporter: shai | Owner: shai
Type: Bug | Status: new
Component: Database layer | Version: 1.6
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: oracle | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by shaib):
I just closed #20647 as a duplicate of this -- that bug is a complaint
about getting a string representation of for-update queries. It fails
becuase the string-representation code uses slicing.
The
[https://code.djangoproject.com/attachment/ticket/20647/20647-test.diff
test code] attached to that ticket should be added when we solve this one,
though.
--
Ticket URL: <https://code.djangoproject.com/ticket/23147#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/062.333f839af8ee750b19d8d584f00462ae%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
