[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2088?page=c...
]
Gail Badner commented on HHH-2088:
----------------------------------
From Steve Ebersole:
It's "ok". Given the current APIs, there is not a better solution at any
rate.
Looking ahead, a better solution is to add a notion of type (org.hibernate.type.Type)
compatibility/comparability. It's funny because the comparability is largely
inconsequential in this particular use case. Here we are much more interested in the
overall number of columns for the type to decide about dialect-proper tuple syntax if
necessary.
TypeMismatchException on object equality expression from one-to-one
relationship
--------------------------------------------------------------------------------
Key: HHH-2088
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2088
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.2.0.cr4
Reporter: Salvatore Insalaco
Attachments: HHH-2088.patch
Suppose to have entity A with a one-to-one constrained relationship to an entity B,
called bRel.
The query: "from A a, B b where a.bRel = b" raises a TypeMismatchException,
even if bRel and b are instances of the same entity.
This happens because in BinaryLogicOperatorNode:
- lhsType is org.hibernate.type.Type = org.hibernate.type.OneToOneType(B)", with
getColumnSpan returning 0.
- rhsType is org.hibernate.type.Type = org.hibernate.type.ManyToOneType(B)", with
getColumnSpan returning 1.
And it compares the two columnspans.
It doesn't happen with 3.2.0.cr2.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira