From: Christian B. (JIRA) <no...@at...> - 2006-05-26 13:30:36
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HB-123?page=all ] Christian Bauer resolved HB-123: -------------------------------- Resolution: Won't Fix This is all done in Hibernate 3.2. You can use a DISTINCT keyword or a ResultTransformer to hide the duplicates, if you want to. The new DISTINCT keyword filters the duplicate root entities in memory. Of course there is no way to "hide" them at the SQL row level, and that is also why thy are exposed by default. > Apply distinctness to HQL fetch of collection > --------------------------------------------- > > Key: HB-123 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-123 > Project: Hibernate2 > Type: Improvement > Components: core > Versions: 2.0 final > Reporter: Steve Knight > Priority: Minor > > > HQL fetch of an associated collection should return distinct entities. > For example, the following HQL: > "FROM Department dept LEFT JOIN FETCH dept.personnel" > should return each department(with its associated collection) only once. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |