[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2766?page=c...
]
Ilhan Nisamedtinov commented on HHH-2766:
-----------------------------------------
Ok, yes it works. But is it possible to initialize this enhancement by HQL query FETCH
JOIN construction or only through separate select initialized by Hibernate.initialize call
for given association of previously returned entity? I could not initialize associations
with HQL, may be it's not even possible I trying to do?
many-to-one with property-ref run into an recursive issue
---------------------------------------------------------
Key: HHH-2766
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2766
Project: Hibernate3
Issue Type: Bug
Components: core
Affects Versions: 3.2.5
Environment: Hibernate 3.2.5, Informix 10
Reporter: René Fuchs
With many-to-one and property-ref, hibernate resolve always the whole referenced entity.
So we have alway an eager issue. If the resolved entity includes one or more other
references to non primary keys,
these entities will be also resolved and so on.
In a big legacy database, if I read only one entity, I get 100 selects or a very very
long joined sql (fetch="join").
I think the problem ist located in:
org.hibernate.type.EntityType
public Object resolve(Object obj, SessionImplementor sessionimplementor, Object obj1)
--
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