[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2473) fetch="join" and property-ref
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473?page=c...
]
Dilip Dalton commented on HHH-2473:
-----------------------------------
This problem also occurs even if the property-ref entity is eagerly fetched. A separate
SQL is issued for each entity referred by the property-ref. This is causing performance
issues while loading the data.
Unfortunately the alternatve method of using the "foreign" id generator cannot
be used because we have existing data and the ids are not the same between the entities in
the one-to-one relationship.
So please treat this with high priority. We are even considering to completely bypass
hibernate as the performance is bad.
fetch="join" and property-ref
-----------------------------
Key: HHH-2473
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473
Project: Hibernate3
Issue Type: Improvement
Affects Versions: 3.2.1
Environment: Version 3.2.1, not DB dependant
Reporter: David CLEMENT
When Hibernate does a fetch join with a property-ref in a many-to-one, it issues the
join SQL query but needs another select to find the associated entity by property-ref.
It should be able to use the entity fetched in the join instead (maybe this has been done
to ensure the unicity of the associated entity, but it introduce a performance issue).
--
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