[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-304) Subselect fetching with setMaxResults()

[Vikram Naik (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43208#comment-43208 ] 

Vikram Naik commented on HHH-304:
---------------------------------

Gavin,

We are facing the same issue with Hibernate 3.6.3.Final, there is another JIRA around the same issue at https://hibernate.onjira.com/browse/HHH-2666

The fetch strategy of "subselect" is extremely useful to avoid (N+1) selects and greatly enhances the response time. 

Would be grateful if we could get a patch release for this issue.

Thanks.

> Subselect fetching with setMaxResults()
> ---------------------------------------
>
>                 Key: HHH-304
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-304
>             Project: Hibernate Core
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.0 final
>            Reporter: Gavin King
>            Assignee: Gavin King
>
> Any limit that gets applied to a query should also get applied to the subselect of any subsequent collection fetches.
> Also, we need to make sure that a newly inserted collection that shows up in the subselect fetch resultset gets ignored by Loader.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira