-
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 not supporting IN parameters with DB2 #3165
Comments
Related to #3085. Have you picked up our latest Spring Data release (either https://spring.io/blog/2023/09/15/spring-data-2023-1-0-m3-released or https://spring.io/blog/2023/09/15/spring-data-2023-0-4-2022-0-10-and-2021-2-16-released), because we have a patch that stops mangling named queries, which looks like what may have happened to you. Or...it may have nothing to do with you given you are using a stored procedure. |
could not find latest dependency out there on maven. any temporary fix? |
If you would like us to spend some time helping you to diagnose the problem, please spend some time describing it and, ideally, providing a minimal yet complete sample that reproduces the problem. |
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,
My Procedure call was working fine before spring upgrade.
I am using below dependencies -
org.springframework.boot:spring-boot-starter-data-jpa🫙3.1.3, with which getting
jakarta.persistence:jakarta.persistence-api:jar:3.1.0
Now, when I call this in code, I am getting below exception.
Db is DB2.
The text was updated successfully, but these errors were encountered: