Re: Unexpected error when calling stored procedure.
Posted by: John Cuyle
Date: February 28, 2020 01:30PM

It's executed as a single statement. CALL proc( arg, arg, arg); It shouldn't need multiQuery, and doesn't when using the C++ Connector. I'd also expect that if it did, the command would not get as far as the database. If someone is trying to perform an injection attack, failing after the query has been executed would be sub-optimal. At any rate, enabling it does not change the behavior. Same (unhelpful) error.

Options: ReplyQuote

Written By
Re: Unexpected error when calling stored procedure.
February 28, 2020 01:30PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.