From: Emmanuel B. (JIRA) <no...@at...> - 2006-07-09 09:16:57
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1890?page=all ] Emmanuel Bernard updated HHH-1890: ---------------------------------- Component: core Summary: setMaxResult, distinct, joined collections optimization (was: setMaxResult, distinct, ) Description: As discussed months ago. Instead of the current behavior, we can apply the first/max operations on the distinct ids and retrieve the fully loaded object graph from it, either: - creating a temp table, populating this temp table with insert ... select id from (my original query), retrieving elements select from [my join path} where root.id in (select temp table with first / max restriction) - or using a subselect (not sure it works for every cases Version: 3.2.0.cr3 > setMaxResult, distinct, joined collections optimization > ------------------------------------------------------- > > Key: HHH-1890 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1890 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.2.0.cr3 > Reporter: Emmanuel Bernard > > > As discussed months ago. > Instead of the current behavior, we can apply the first/max operations on the distinct ids and retrieve the fully loaded object graph from it, either: > - creating a temp table, populating this temp table with insert ... select id from (my original > query), retrieving elements select from [my join path} where root.id in (select > temp table with first / max restriction) > - or using a subselect (not sure it works for every cases -- 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 |