-
Notifications
You must be signed in to change notification settings - Fork 195
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
Call Function with INOUT-Null-Value #1420
Comments
Additional information, the issue can be workaround, with
|
Possibly related to #1246 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version:
Vert-X: 4.5.4
Oracle-JDBC: 19.18.0.0
Issue:
In case of database-procedure and the parameter is defined as an INOUT and the input-value is NULL, the wrong type is passed to JDBC-Driver. It makes no different if the tuble-parameter is set to
The JDBC-Driver everytime response with Parameter type conflict. The Input-Part is set to VARCHAR, the Output to TINYINT, regardless, what is defined within the Tuble-Parameter.
Do you have a reproducer?
I pushed a rep-case to Github:
Rep-Case-NullValue
The test.sql contains the package, just with one INOUT-Parameter.
The text was updated successfully, but these errors were encountered: