6:14 a.m.
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
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3524) setFetchMode ignored if using createCriteria
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3524?page=c...
]
Gail Badner commented on HHH-3524:
----------------------------------
Peter, are you using the query cache? If so, this is a known issue.
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
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:55 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3524) setFetchMode ignored if using createCriteria
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3524?page=c...
]
Peter Weemeeuw commented on HHH-3524:
-------------------------------------
Hi Gail,
No, the query cache is set to false in my hibernate properties.
Regards,
Peter
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
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-3524) setFetchMode ignored if using createCriteria
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3524?page=c...
]
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:49 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3524) setFetchMode ignored if using createCriteria
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3524?page=c...
]
Richard Ogin commented on HHH-3524:
-----------------------------------
I found a workaround to the problem: specify the joinType as LEFT_OUTER_JOIN when creating
a sub-criteria (the default was INNER_JOIN for 3.2.6.ga).
Example:
rootCriteria.createCriteria("foos",
org.hibernate.sql.JoinFragment.LEFT_OUTER_JOIN).add( Restrictions.eq("bar",
barValue) );
rootCriteria.setFetchMode("foos", FetchMode.JOIN);
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:46 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3524) setFetchMode ignored if using createCriteria
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3524?page=c...
]
Stian Brattland commented on HHH-3524:
--------------------------------------
I'm having the exact same problem using Hibernate 3.2.5.ga and MySQL 5.1. I have
disabled the query cache.
The workaround introduced by Richard Ogin does not work for me. I can confirm that
invoking createCriteria() or createAlias() on any existing Criteria object makes
Hibernate ignore everything that has been set through setFetchMode().
The following Criteria succeeds:
Criteria a = getSession().createCriteria(AlbumHierarchyNode.class);
a.setFetchMode("albums", FetchMode.JOIN).setFetchMode("albums.album",
FetchMode.JOIN).setFetchMode("albums.album.library", FetchMode.JOIN);
a.add(Restrictions.isNotNull("parent"));
a.setResultTransformer(Criteria.DISTINCT_ROOT_ENTITY);
a.list();
The following Criteria fails:
Criteria a = getSession().createCriteria(AlbumHierarchyNode.class);
a.setFetchMode("albums", FetchMode.JOIN).setFetchMode("albums.album",
FetchMode.JOIN).setFetchMode("albums.album.library", FetchMode.JOIN);
a.createCriteria("albums").createCriteria("album").add(Restrictions.in("status",
filter.getStatuses()));
a.add(Restrictions.isNotNull("parent"));
a.setResultTransformer(Criteria.DISTINCT_ROOT_ENTITY);
a.list();
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:53 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3524) setFetchMode ignored if using createCriteria
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3524?page=c...
]
Richard Ogin commented on HHH-3524:
-----------------------------------
@Stian
You need to specify JoinFragment.LEFT_OUTER_JOIN in your createCriteria() from the root
node. To use your example, a.createCriteria("albums") would become
a.createCriteria("albums", JoinFragment.LEFT_OUTER_JOIN).
To use my code as an example:
Criteria c = session.createCriteria(Company.class);
c.createCriteria("addresses", JoinFragment.LEFT_OUTER_JOIN).add(
Restrictions.ilike("state", state, MatchMode.EXACT) );
c.setFetchMode("addresses", FetchMode.JOIN);
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:09 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3524) setFetchMode ignored if using createCriteria
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3524?page=c...
]
Lindsey Carriere commented on HHH-3524:
---------------------------------------
@Richard, thanks for the workaround. I spent days trying to figure this out.
I have found that even using JoinFragment.INNER_JOIN doesn't work (runs N+1 queries on
the collections with my openSessionInView filter enabled), yet the LEFT_OUTER_JOIN works
as expected only running one query. HQL does not have this problem at all, INNER JOIN
FETCH works as expected.
See my post on the forums for full details if needed.
https://forum.hibernate.org/viewtopic.php?f=1&t=999780&start=0
Have any developers confirmed this bug yet? I need a fix ASAP.
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:13 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3524) setFetchMode ignored if using createCriteria
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3524?page=c...
]
Lindsey Carriere commented on HHH-3524:
---------------------------------------
Also, this issue was seen in 3.0, 3.1 and 3.3.2GA. Also, createCriteria and createAlias
behave the same way. Thanks.
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:03 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3524) setFetchMode ignored if using createCriteria
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3524?page=c...
]
Christian Bourque commented on HHH-3524:
----------------------------------------
Weird because if you explicitly set the join mode to left join, you don't need the
fetch mode at all:
Criteria c = session.createCriteria(Company.class);
c.createCriteria("addresses", Criteria.LEFT_JOIN);
c.list();
Tested on 3.3.2.GA and 3.5.0.Beta-1...
Thanks
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:29 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3524) setFetchMode ignored if using createCriteria
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3524?page=c...
]
errorken commented on HHH-3524:
-------------------------------
I'm seeing the exact same problems as described here.
If I create a Criteria which executes two joins (one inner join and one outer join) on
two set collection then both are eagerly fetched automatically.
This is in contradiction with the HQL equivalent, where an explicit 'fetch' is
required to do this.
Futher more, setting the fetch type to SELECT (either on the root criteria or sub criteria
if you are using them) doens't work.
I was trying to trigger the LazyInitializatoinExcepion by setting the fetch type to SELECT
and then hitting the collection after TX end.
When I replaced the criteria code with HQL: it goes as expected, I get the
LazyInitException when I remove on of the two "fetch" keywords in the query.
The setFetchMode in combination with the Criteria API the fetch type seems to be
completely fubar.
Also; the setFetchType does not throws errors when the association path does not exist, it
just takes any string and it never does a thing.
Thanks
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:42 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-3524) setFetchMode ignored if using createCriteria
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3524?page=c...
]
Gail Badner updated HHH-3524:
-----------------------------
Affects Version/s: 3.6.0.CR1
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.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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:37 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-3524) setFetchMode ignored if using createCriteria
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3524?page=c...
]
Mert Can Akkan commented on HHH-3524:
-------------------------------------
this issue is still active on 3.5.1 - 3.5.5 and it simply killer bug for criteria api
PS: hibernate entity manager (JPA) criteria api does not have same error.
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.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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:40 a.m.
New subject: [Hibernate-JIRA] Updated: (HHH-3524) setFetchMode ignored if using createCriteria
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3524?page=c...
]
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4925
days inactive
5744
days old
hibernate-issues@lists.jboss.org
13 comments
8 participants
participants (8)
-
Christian Bourque (JIRA) -
errorken (JIRA)
-
Gail Badner (JIRA)
-
Lindsey Carriere (JIRA)
-
Mert Can Akkan (JIRA)
-
Peter Weemeeuw (JIRA)
-
Richard Ogin (JIRA)
-
Stian Brattland (JIRA)