[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2921?page=c...
]
Johan Hoogenboezem commented on HHH-2921:
-----------------------------------------
This turns it into a chicken-egg problem. I need to evict the proxy, but I need to run the
query to get the proxy.
Otherwise I have to dig through the rest of the code running in the same transaction and
find the place where the proxy was being placed into the session and evict it there.
Wouldn't the Hibernate code be the best place for the eviction of the entity from the
session?
I think this forces developers to know more about the internals of Hibernate than they
need to.
Polymorphic query breaks if entity proxy already exists in session
------------------------------------------------------------------
Key: HHH-2921
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2921
Project: Hibernate3
Issue Type: Bug
Components: core
Affects Versions: 3.2.5
Environment: 3.2.5, PostgreSQL 8.1.2, jdk1.5.0_08, Windows XP
Reporter: Johan Hoogenboezem
Assignee: Gail Badner
I posted to the user forum about this on Oct 26
(
http://forum.hibernate.org/viewtopic.php?t=980752). I've had no reply. This is a
serious hassle for me, so I submit it as a bug.
--
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