#23766 closed Cleanup/optimization (fixed)
Documentation and tests for cursor.callproc()
| Reported by: | Shai Berger | Owned by: | Mariusz Felisiak |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | averybigant | Triage Stage: | Accepted |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
This is a spin off #23546 -- actually, a requirement for that ticket.
Quoting my 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 pep249; this allows database stored procedures to be called.
Recently [...] we found that
cursor.callproc()is not documentedcursor.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.
Change History (7)
comment:1 by , 11 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 9 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 9 years ago
I would like to resolve this issue, but it seems that we don't have appropriate place for cursor.callproc in the documentation. Any suggestions?
comment:4 by , 9 years ago
Perhaps near the Connections and cursors section? Anyway, getting a draft of the content is most of the work; it can be moved if needed.
Agreed. This should be documented and tested.