[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473?page=c...
]
FATEC commented on HHH-2473:
----------------------------
sorry to comment again, but this is a big problem in our project, because hibernate does N
selects instead of only 1 select
when this bug will be fixed ?
thanks
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