[hibernate-issues] [Hibernate-JIRA] Created: (HHH-2480) Unify join fetch behavior or HQL and Criteria APIs

Christian Bauer (JIRA) noreply at atlassian.com
Fri Mar 9 11:11:09 EST 2007


Unify join fetch behavior or HQL and Criteria APIs
--------------------------------------------------

         Key: HHH-2480
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2480
     Project: Hibernate3
        Type: Improvement

  Components: query-hql, query-criteria  
    Reporter: Christian Bauer
    Priority: Critical
     Fix For: 3.3


Can we consider changing the criteria API in 3.3 so that DISTINCT_ROOT_ENTITY is the default transformer?
10:28
I remember that detecting "fetch" in HQL and applying this transformer is already on the list, right?
10:29
or introduce config options for both APIs, so users can switch the default transformer
10:30
also, verify this please: http://www.hibernate.org/117.html#A12

Steve
2:31
we should try to detect if any fetches are present
2:31
otherwise DISTINCT_ROOT_ENTITY presents unecessary overhead
2:31
i dont recall such a discussion regarding that  feature in HQL
2:32
another option is sorta like i'm planning in other areas: fallback to subselect fetching


-- 
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




More information about the hibernate-issues mailing list