JPA positional parameter mapping bug with" same java type and same value but different custom type"

Description

  1. some JPA positional parameters have same position(?1)

  2. the condition columns' java type is the same and the parameter value is the same

  3. but the columns have different custom types
    Then parameter mapping works wrong.

example Entity mapping

example HQL query

Real query parameter mapping

  1. 'T'

  2. 'T' -> This must be 'Y' because second parameter custom type is 'yes_no'

  3. FALSE

I made a sample project to reproduce this bug.
https://github.com/kwon37xi/hibernate-customtype-same-value-binding-bug

Environment

Java 7, mysql, h2 databases

Assignee

Unassigned

Reporter

KwonNam Son (손권남)

Fix versions

None

Labels

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Components

Affects versions

Priority

Major
Configure