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
But when I get result for "v3", the value is always 0, and I follow the source code(not very carefully), I think jdbi will overwrite the parameter, when bind and registerOutParameter use the same name.
So is there any solution for invoking a procedure, when procedure has a paremeter is both in and out ?
The text was updated successfully, but these errors were encountered:
I think you're right, this doesn't work right. Figuring out what's wrong is hampered by both the h2 and pg-jdbc drivers not fully supporting named callable parameters... I started hacking here https://github.com/jdbi/jdbi/tree/call-inout but no fix yet.
@joshua-jin This generally happenes when you use select statement in stored procedure on db side to return a value, Try replacing your select with return statement if not already ??
I have a procedure in Oracle like this:
and my java code is:
But when I get result for "v3", the value is always 0, and I follow the source code(not very carefully), I think jdbi will overwrite the parameter, when
bind
andregisterOutParameter
use the same name.So is there any solution for invoking a procedure, when procedure has a paremeter is both in and out ?
The text was updated successfully, but these errors were encountered: