[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1499?page=all ]
Steve Ebersole updated HHH-1499:
--------------------------------
Fix Version: hql+collection
(was: 3.2.2)
use subselect fetching for collection join fetches with DISTINCT or
firstResult/maxRows
---------------------------------------------------------------------------------------
Key: HHH-1499
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1499
Project: Hibernate3
Type: Improvement
Components: query-hql
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: hql+collection
As a follow on to HHH-1411and HHH-1412...
Both of those above were actually resolved by handling the DISTINCT-ion and/or
firstResult/maxRows *in memory*. A better solution is to not honor the join fetch in
these cases, perform the requested operation, and then get the requested join fectehd
collections through subselect fetches.
As is, this would work as long as the collections have subselect fetching enabled in
metadata, but would actually use immediate fetching (n+1) for any collections not defining
subselect fetching in metadata. This is due to the way
PersistenceContext.initializeNonLazyCollections() currently works.
--
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