[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-3524) setFetchMode ignored if using createCriteria

[Richard Ogin (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Ogin updated HHH-3524:
------------------------------

    Attachment: test.case.tar.gz

The reporter's example uses DetachedCriteria. Here is a test case utilizing "normal" criteria (and CacheMode.IGNORE).

> setFetchMode ignored if using createCriteria
> --------------------------------------------
>
>                 Key: HHH-3524
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3524
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: query-criteria
>    Affects Versions: 3.2.5
>         Environment: Hibernate 3.2.5, Oracle 8
>            Reporter: Peter Weemeeuw
>         Attachments: test.case.tar.gz
>
>
> Hi,
> It seems that criteria.setFetchMode gets ignored if you combine it with createCriteria to add a restriction.
> This works as expected:
> DetachedCriteria c = DetachedCriteria.forClass(MenuItem.class);
> c.setFetchMode("menuItemSubscriptions", FetchMode.JOIN);
> But in this case the join doesn't happen (and I get a LazyInstantiationException further on).
> DetachedCriteria c = DetachedCriteria.forClass(MenuItem.class);		
> c.setFetchMode("menuItemSubscriptions", FetchMode.JOIN);
> c.createCriteria("menuItemSubscriptions").add(
> 	Restrictions.eq("location", "B")
> );
> This does not happen if I set lazy="false" in the mappings
> file.
> Regards,
> Peter

-- 
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