-
Notifications
You must be signed in to change notification settings - Fork 866
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
QueryDSL-JPA + Custom type implementing Number + NumberExpression #3550
Comments
I’m not so sure if Converters ever “worked as intended” for Hibernate 5 as well: #2652 The problem is that the JPA specification doesnt really specify how converted fields should be treated in JPQL, leading to different expectations and implementations in JPA vendors. |
Hi, I have forked this project and we just released a released a milestone to maven central that is compatible with hibernate 6. If you can, please try Also note the artifact GAV changed:
|
I just tried your fork and switched from Would you like me to continue this bug-report on your forked repo? |
Yes please |
Discussion continued on the OpenFeign issue |
To all coming here from google: the bug is not related to Hibernate 6 but a custom type somehow implementing |
Observed vs. expected behavior
When using the following Combination
Example:
Actual outcome:
I receive
java.lang.IllegalArgumentException: Unsupported target type : MyCustomNumber
instead of a valid result.Expected outcome:
The query-result.
Steps to reproduce
I created a reproducer with unit tests showing what works and what doesn't:
https://github.com/dvbern/bug-reproducers-querydsl-jpa-hibernate6
Environment
Querydsl version: 5.0.0-jakarta (does not look like a jakarta-problem, though)
Querydsl module: querydsl-jpa/querydsl-core
Database: any (e.g. hsqldb, postgresql)
JDK: 17 (but the stacktrace indicates this is not a JDK-problem)
Additional details
Works correctly - at least "as expected" :) - in the old Hibernate 5.(Edit: QueryProjection and Hibernate6 is not necessary. I updated Description + Title accordingly)
The text was updated successfully, but these errors were encountered: