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

umanath kandhallu (JIRA) noreply at atlassian.com
Fri Jan 20 00:28:12 EST 2012


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

umanath kandhallu commented on HHH-304:
---------------------------------------

i used following as a work around 

@Fetch(FetchMode.JOIN)
@BatchSize(size=200)

so the generated query was like 

select * from child where parentid in (?,?,?...)

instead of

select * from child where parentid in (criteria query which used to select parent)


> Subselect fetching with setMaxResults()
> ---------------------------------------
>
>                 Key: HHH-304
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-304
>             Project: Hibernate ORM
>          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

        


More information about the hibernate-issues mailing list