#20516: Allow use of prepared statements
-------------------------------------+-------------------------------------
Reporter: est | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: db, prepared | Triage Stage: Accepted
statement |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by shaib):
On Oracle, the concept of prepared statements is linked to a connection-
level statement cache. Prepared statements are not handled with different
SQL, but with different API calls -- specifically, cx_Oracle provides a
[http://cx-oracle.readthedocs.org/en/latest/cursor.html#Cursor.prepare
prepare] method on its cursors. This method is not currently used by
Django's Oracle backend.
--
Ticket URL: <https://code.djangoproject.com/ticket/20516#comment:13>
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/061.4ccd01df69f3d931115d62326c8346bd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
