-
Notifications
You must be signed in to change notification settings - Fork 436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stored Procedures #16
Comments
It should be possible to call stored procedures now, but in a quite limited way. If you don't need any output parameters, then you can use a For example, Input parameters can passed using string concatention.
Of course this is horrible, and not a good strategy. Issue #14 will introduce support for execution of parameterised requests, which will remove the need for that approach. I intend to work on it soon, and expect it to be in the next release. It will only support a small number of data types for parameters intially. Once parameterised requests are in place, it shouldn't require too much work to provide a decent API for execution of stored procedures. |
I don't mind running "exec my_proc" strings as SQL statements; it seems to work except the row count comes back undefined in these cases. |
Support for executing stored procedures, including passing input and output parameters has been added. The documentation has not been updated yet. |
Could you post a sample code to call a stored procedure using input/output parameters? |
Note: I am not convinced that the API is quite right. There's a good chance that it will change. |
Thanks! |
Please note, the first two arguments to the
|
Included in v0.0.4. |
I don't know if you already have support for calling stored procedures. If you do, how do you call them? If not, would it take much effort to add support for stored procedures? Thanks!
The text was updated successfully, but these errors were encountered: