You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DBAPI provides following method to call stored procedures.
.callproc( procname [, parameters ] )
(This method is optional since not all databases provide stored procedures. [3])
Call a stored database procedure with the given name. The sequence of parameters must contain one entry for each argument that the procedure expects. The result of the call is returned as modified copy of the input sequence. Input parameters are left untouched, output and input/output parameters replaced with possibly new values.
The procedure may also provide a result set as output. This must then be made available through the standard .fetch*() methods.
Describe alternatives you've considered
No response
Are you willing to submit PR?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered:
I don't think those are "stored procedures" regardless of what the docs say.
@martint / @dain Once/when SQL defined functions land do we expect to reuse the CALL statement to execute those?
I'd like to avoid a situation where we need to change what callproc does once SQL defined functions/SPs are available since it'd break user code.
Describe the feature
DBAPI provides following method to call stored procedures.
Describe alternatives you've considered
No response
Are you willing to submit PR?
The text was updated successfully, but these errors were encountered: