-
Notifications
You must be signed in to change notification settings - Fork 41.2k
Second call to query method of JpaRepository fails with Hibernate 5.6.6 since Spring Boot 2.6.5 #30421
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
Comments
This is a duplicate of spring-projects/spring-data-jpa#2472. As discussed in that issue, overriding the Hibernate version to |
Since this issue makes the runtime error and not the compile error, I think that spring-boot team should release a micro version with downgraded hibernate version even if there is a workaround (not known by many). |
We can't do that as downgrading would expose everyone using Hibernate to all of the bugs that have been fixed since 5.6.5, some of which may not have a workaround. If using 5.6.5 is a better option for you than using 5.6.7 with a workaround for this specific problem, you should opt into that arrangement by overriding the Hibernate version. |
Hello, Thanks in advance |
We have 2.5.x and 2.6.x releases planned this week which, all being well, will include Hibernate 5.6.9. |
Since migration to Spring Boot 2.6.5, calls to JpaRepository query method fail with exception
java.lang.IllegalArgumentException: Parameter value [\] did not match expected type [java.lang.String (n/a)]
.The issue is reproduced in unit test of reproducer project https://github.com/fstaudt/sb265-hibernate-failure :
findAllByNameContaining(...)
succeedsUnit tests pass if Spring Boot version is reverted to 2.6.4.
Issue can also be reproduced at runtime (tested with bootRun), it is not only in unit tests.
I wasn't able to identify the root cause.
I'm not sure that issue is actually in Spring Boot (might as well be in Spring Data or in Hibernate).
The text was updated successfully, but these errors were encountered: