Improves SimpleJdbcCall when targeting the Oracle database:
-
Improve support of Oracle PL/SQL packages for Spring JDBC: Oracle database stored procedures or functions can be overloaded. Hence, the possibility to find several matching signatures by just using the schema name, catalog name and procedure/function name is real. This PR adds columns data type checking to properly find the desired stored procedure or function.
-
Ease debugging for DBMS_ packages if SYS not specified: explicitly checks the catalog name being used and if starting with DBMS_% and no matching signature was found then report in the log it could be useful to use SYS as the schema name
Comment From: snicoll
@loiclefevre please refrain from opening duplicate PRs. If you need to amend your existing PR, pushing to an existing branch will update your existing PR. As you've created the PR from main, it might close itself if you upgrade the remote but you can reopen the PR and push force it.
Comment From: loiclefevre
Hello, do you have any news regarding this PR? Thanks
Comment From: snicoll
I am afraid not. The team is busy on other themes lately and we didn't get a chance to look at it yet.
Comment From: loiclefevre
I am afraid not. The team is busy on other themes lately and we didn't get a chance to look at it yet.
Is there any way I can help, maybe? Thing is, this one really simplifies integration with Oracle PL/SQL world (I mean from a developer standpoint).
Comment From: snicoll
Unfortunately, I don't think we can consider this PR due to the amount of breaking change it brings. Would you be willing to provide an update that doesn't break existing signatures?
Comment From: snicoll
Closing due to lack of requested feedback. If the feedback is provided we can consider reopening.