5:11 p.m.
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
5:11 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-2480) Unify join fetch behavior for HQL and Criteria APIs
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2480?page=all ]
Christian Bauer updated HHH-2480:
---------------------------------
Summary: Unify join fetch behavior for HQL and Criteria APIs (was: Unify join fetch
behavior or HQL and Criteria APIs)
Unify join fetch behavior for 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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
5:32 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-2480) Unify join fetch behavior for HQL and Criteria APIs
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2480?page=c...
]
Steve Ebersole updated HHH-2480:
--------------------------------
Affects Version/s: antlr-rework
Unify join fetch behavior for HQL and Criteria APIs
---------------------------------------------------
Key: HHH-2480
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2480
Project: Hibernate3
Issue Type: Improvement
Components: query-criteria, query-hql
Affects Versions: antlr-rework
Reporter: Christian Bauer
Priority: Critical
Fix For: antlr-rework
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:32 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-2480) Unify join fetch behavior for HQL and Criteria APIs
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2480?page=c...
]
Steve Ebersole updated HHH-2480:
--------------------------------
Fix Version/s: (was: 3.3)
antlr-rework
Unify join fetch behavior for HQL and Criteria APIs
---------------------------------------------------
Key: HHH-2480
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2480
Project: Hibernate3
Issue Type: Improvement
Components: query-criteria, query-hql
Affects Versions: antlr-rework
Reporter: Christian Bauer
Priority: Critical
Fix For: antlr-rework
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:23 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2480) Unify join fetch behavior for HQL and Criteria APIs
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2480?page=c...
]
wesley wu commented on HHH-2480:
--------------------------------
I need this improvement especially when I use EntityManager to do query rather than
Criteria or HQL.
In fact, the HibernateEntityManager provides no way to force returning distinct top level
pojo objects when there is an One-to-Many left outer join clause.
One of the workaround I learned from http://www.hibernate.org/117.html#A12 is to add a
DISTINCT keyword after SELECT.
"Yes, in other cases an HQL distinct will translate straight into a SQL DISTINCT. Not
in this case: you can not filter out duplicates at the SQL level, the very nature of a
product/join forbids this - you want the duplicates or you don't get all the data you
need."
But in two cases, this workaround failed to work:
1. When the resultset should be paginated, I.E., setFirstResult() and setMaxResults()
were used.
2. When the resultset has LONGVAR field, like ntext, image in SQLServer. Database will
generate a error like : ntext datatype could not be distinct compared."
And these two case should happen pretty frequently.
The conclusion : despite of using
"setResultTransformer(Criteria.DISTINCT_ROOT_ENTITY)" in Hibernate HQL queries
and criteried queries, HibernateEntityManager has no way to eliminate the duplication of
top level pojo objects when there is an One-to-Many left outer join clause.
We need this improvments indeed.
Thanks in advance.
Unify join fetch behavior for HQL and Criteria APIs
---------------------------------------------------
Key: HHH-2480
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2480
Project: Hibernate3
Issue Type: Improvement
Components: query-criteria, query-hql
Affects Versions: antlr-rework
Reporter: Christian Bauer
Priority: Critical
Fix For: antlr-rework
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:42 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-2480) Unify join fetch behavior for HQL and Criteria APIs
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2480?page=c...
]
Mindaugas Plukas commented on HHH-2480:
---------------------------------------
This issue may be related to
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4658
Unify join fetch behavior for HQL and Criteria APIs
---------------------------------------------------
Key: HHH-2480
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2480
Project: Hibernate Core
Issue Type: Improvement
Components: query-criteria, query-hql
Affects Versions: antlr-rework
Reporter: Christian Bauer
Priority: Critical
Fix For: antlr-rework
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5313
days inactive
6321
days old
hibernate-issues@lists.jboss.org
5 comments
4 participants
participants (4)
-
Christian Bauer (JIRA) -
Mindaugas Plukas (JIRA)
-
Steve Ebersole (JIRA)
-
wesley wu (JIRA)