#23766: Documentation and tests for cursor.callproc()
-------------------------------------+-------------------------------------
Reporter: shaib | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master
Component: Database | Keywords:
layer (models, ORM) | Has patch: 0
Severity: Normal | Needs tests: 0
Triage Stage: | Easy pickings: 0
Unreviewed |
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
This is a spin off #23546 -- actually, a requirement for that ticket.
Quoting my [https://groups.google.com/d/msg/django-
developers/v3AhQhJFhGM/TScISVjLBQoJ message] to -developers on the subject
(the thread trails off to discussions of higher-level interfaces, but the
following seems to be in consensus):
For a very long time -- as far as I'm aware, forever -- we've had, in our
cursor classes, a `callproc()` method that follows the `callproc()`
definition of [http://legacy.python.org/dev/peps/pep-0249/#callproc
pep249]; this allows database stored procedures to be called.
Recently [...] we found that
1. `cursor.callproc()` is not documented
2. `cursor.callproc()` is not tested (except for one Oracle-specific
test that uses it to test something else)
Which means, essentially, that it is treated as an intenal API.
I see no reason that we shouldn't make it public.
--
Ticket URL: <https://code.djangoproject.com/ticket/23766>
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/048.4ebdc14d6dbceb90dfc14681ae19b7c5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
