[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473?page=c...
]
Gary Sargent commented on HHH-2473:
-----------------------------------
Isn't this a bug rather than an improvement?
Hibernate should have all the data it needs as it has done the outer join to get the
entities involved. It does not need to do N selects to get the data again.
Just because property-ref is being used in the many-to-one should make no difference to
when the id is used.
This does have a bad performance implication. Can anyone from the Hibernate team comment?
fetch="join" and property-ref
-----------------------------
Key: HHH-2473
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473
Project: Hibernate Core
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