[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-123) Apply distinctness to HQL fetch of collection

[Mattias J. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HB-123?page=comments#action_23480 ] 

Mattias Jiderhamn commented on HB-123:
--------------------------------------

> Of course there is no way to "hide" them at the SQL row level, and that is also why thy are exposed by default.

If eager fetching of collections is disabled one could use SQL DISTINCT (unless there is something here I don't see).
I have no idea whether that that would (generally) perform better than eager fetching and filtering in Java.
(Maybe this could be an option, globally or per query???)

> 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