-
Notifications
You must be signed in to change notification settings - Fork 66
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
Support for sql.Out parameters #232
Comments
sql.Out is not supported yet. |
Thanks for the reply!
I do use what you’ve suggested already.
My intention, however, was to stay within database.sql paradine. However, I could not find a way to execute a statement that returns a cursor(s) using this package.
Ideally, for me :), I’d love to have a way to call sql.Exec with out params that are sql.Rows.
Do you think there’s any way on earth that we could accomplish this?
I’d gladly volunteer myself to this task if you have an idea what would be the implementation approach....
Cheers,
LK
… On Nov 12, 2017, at 4:23 PM, Tamás Gulácsi ***@***.***> wrote:
sql.Out is not supported yet.
Use &ora.Rset as parameters, and then their methods to retrieve the rows.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I see!
Thanks a lot.
If you need any help, please, count me in :)
Cheers,
LK
… On Nov 13, 2017, at 11:53 AM, Tamás Gulácsi ***@***.***> wrote:
I'm waiting for suggestions:
https://groups.google.com/forum/#!topic/golang-sql/HNvcgScdyt8
https://groups.google.com/forum/#!topic/golang-nuts/-mIE85Pde5E
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Suppose that I'm calling a stored procedure via database.sql and I have a number of output parameters, each of which is a cursor. Is there support for this in this package?
I mean something like this:
The text was updated successfully, but these errors were encountered: