-
Notifications
You must be signed in to change notification settings - Fork 108
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
json_proc_param_out_cursor example from rest-sql/demo-all-in-one.html blame on "Parameter Type Conflict" #26
Comments
Perhaps ORDS use wrong casting in java for parameter of OracleTypes.CURSOR type. VARIABLE refcur REFCURSOR works like a charm: { |
May be OracleCallableStatement did a trick in place of CallableStatement. |
Trying ORDS 19.1 in front of Oracle EE 12.1.0.2 with rest-sql/demo-all-in-one.html samples.
Got this in reply:
{
"env": {
"defaultTimeZone": "GMT"
},
"items": [
{
"statementId": 1,
"statementType": "sqlplus",
"statementPos": {
"startLine": 1,
"endLine": 1
},
"statementText": "exec ADHOC_PROC_SIMPLE_OUT_CURSOR(?)",
"response": [
"\nError starting at line : 1 in command -\nBEGIN ADHOC_PROC_SIMPLE_OUT_CURSOR(:adhocbind1); END;\nError report -\nParameter Type Conflict\n"
],
"errorCode": 17012,
"errorLine": 1,
"errorColumn": 0,
"errorDetails": "Parameter Type Conflict",
"result": 0,
"binds": [
{
"index": 1,
"data_type": "CURSOR",
"mode": "out",
"result": null
}
]
}
]
}
The text was updated successfully, but these errors were encountered: