[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3409?page=c...
]
Steve Ebersole commented on HHH-3409:
-------------------------------------
And you cannot just start dropping public APIs from widely used libraries :)
In regards to your last comment, yes for performance the hashCode is cached as part of the
state of QueryKey. However, a far more reasonable solution imo seems to be to make that
field transient and to just recalculate it on deserailization instead. Far better than
relying some custom user ResultTransformer implementation's hashCode()
ResultTransformers need smarter equals() and hashCode() impls
-------------------------------------------------------------
Key: HHH-3409
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3409
Project: Hibernate3
Issue Type: Bug
Components: query-criteria, query-hql
Affects Versions: 3.2.6, 3.3.0.CR1
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 3.2.x, 3.3.0.CR2
Specifically, we need to account for the possibility of distributed query caching
considering that the ResultTransformer is part of the cached query key.
--
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