JPA positional parameter mapping bug with" same java type and same value but different custom type"
Description
Attachments
Activity
KwonNam Son November 14, 2015 at 7:39 AMEdited
This bug affects hibernate 5.0.3.
I attatched a test case.
If you run org.hibernate.bugs.ORMUnitTestCase . This will fail.
Test case source link : https://github.com/kwon37xi/hibernate-5-hhh9871
Steve Ebersole October 28, 2015 at 3:24 AM
As part of verifying that this issue affects 5.0, please just set the "Affects version". Leave the "verify-affects-5.0" label and leave the issue in "Awaiting Response" status; these are critical for us to be able to track these verifications and triage them. Thanks.
Steve Ebersole October 27, 2015 at 7:17 PM
This bug report does not indicate that the reported issue affects version 5.x. Versions prior to 5.x are no longer maintained. It would be a great help to the Hibernate team and community for someone to verify that the reported issue still affects version 5.x. If so, please add the 5.x version that you verified with to the list of affected-versions and attach the (preferably SSCCE) test case you used to do the verification to the report; from there the issues will be looked at during our triage meetings.
For details, see http://in.relation.to/2015/10/27/great-jira-cleanup-2015/
some JPA positional parameters have same position(?1)
the condition columns' java type is the same and the parameter value is the same
but the columns have different custom types
Then parameter mapping works wrong.
example Entity mapping
example HQL query
Real query parameter mapping
'T'
'T' -> This must be 'Y' because second parameter custom type is 'yes_no'
FALSE
I made a sample project to reproduce this bug.
https://github.com/kwon37xi/hibernate-customtype-same-value-binding-bug