[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-3524) setFetchMode ignored if using createCriteria
Gail Badner (JIRA)
noreply at atlassian.com
Mon Jan 10 11:40:05 EST 2011
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gail Badner updated HHH-3524:
-----------------------------
Affects Version/s: 3.3.2
> 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, 3.3.2, 3.6.0.CR1
> 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
More information about the hibernate-issues
mailing list