-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
NamedStoredProcedureQuery: Cannot resolve named output with no input parameters #2188
Comments
We recently rolled out some updates to our support for stored procedures. Can you see if this problem still exists with the latest snapshots? |
Hi! |
For me it works if i make one parameter as ParameterMode.INOUT and then when calling Stored Procedure pass that value as null. |
OpenFindingDTO.java
OpenFindingRepository.java
ReportServiceImpl.java
pom.xml
PRC_OPEN_FINDINGS.sql
As it is cursor, I should take |
This might be resolved via #1759 that used binding details from method parameters and not from |
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed. |
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue. |
Hi there!
I'm not quite sure, but i think i experience an issue using NamedStoredProcedureQuery, calling stored procedures that only have output but no input parameters.
I follwed the example of [DATAJPA-707], defining a NamedStoredProcedureQuery on my Entity
Referencing it in my Repository
When i call this method at runtime, I get an exception:
Climbing up the stack, it seems that useNamedParameters of StoredProcedureJpaQuery is set to false. This is calclulated on startup and is false, because my Repository method has no (named input) parameters. If i set useNamedParameters to true using the debugger, my procedure call works fine. So i guess there should be another option or logic behind this, but may i miss something or this is not an issue in current versions anymore .
Im using spring-data-jpa 2.3.1
Thanks!
Denis
The text was updated successfully, but these errors were encountered: