[Feature Request]: Call DB procedure can't retrieve values over JDBC
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 476
- Avg merge
- 18h 32m
- Merged PRs (30d)
- 216
Description
### What would you like to happen?
The 'Call DB Procedure' transformation, it's impossible to retrieve the return values where we're using JDBC drivers, as stated on the Help Page
"The Call DB Procedure transform allows you to execute a database procedure (or function) and get the result(s) back. With MySQL and JDBC, it is not possible to retrieve the result set of a stored procedure. Stored procedures and functions can only return values through their function arguments and those arguments must be defined in the Parameters section of the DB Procedure Call configuration."
I don't know why this happens, but it's the exactly same phrase and limitation that was present at PentaHo.
There are some other open-source projects that use JDBC and are able to retrieve the values, so it's not an JDBC limitation. For example, DBeaver project.
It's a very big limitation for some use cases, so please can you implement this?
### Issue Priority
Priority: 3
### Issue Component
Component: Transforms
Contributor guide
Research direction
Start with the Call DB Procedure transformation, its JDBC handling, and the Parameters section described in the issue. Compare the current behavior with the referenced Help Page and DBeaver's JDBC procedure handling. Done means defining and validating how result sets or return values are retrieved for MySQL through JDBC.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100