Named query to override eager fetching

[Michael Freake]

Hello,

I'm using Hibernate 3.5 and wondering if it is possible to override the eager loading specified using annotations on a class via a named query?

For example, using the classes below I'd like to use a named query to get a particular course version, it's related course and none of the courses collections.

//..annotations
public class Course {

@OneToMany(cascade=CascadeType.ALL, fetch=FetchType.EAGER)
public List<CourseVersion> getCourseVersions(){
return courseVersionList;

@OneToMany(cascade=CascadeType.ALL, fetch=FetchType.EAGER)
public List<Prerequisite> getPrerequisites(){
return prerequisites;
}
}

//..annotations
public class CourseVersion{

@ManyToOne(...)
public Course getCourse(){
return course;
}

}

//..annotations
public class Prerequisite{

@ManyToOne(...)
public Course getCourse(){
return course;
}

}

[Paul Sturrock]

Yes it is.

[Michael Freake]

Thanks for your reply. It would be very useful if you could provide an example using the above classes so that anyone else who visits this post, including myself, can benefit from it.

Thanks again.

[Michael Freake]

Ok, so I found this: http://ajava.org/online/hibernate3api/org/hibernate/FetchMode.html#SELECT

However, the LAZY fetch mode is now replaced by SELECT, which specifically states that it will perform eager loading... seems like they replaced lazy loading with the exact opposite to me, but I could be wrong.

[Michael Freake]

Ok, it appears Paul's comment above is incorrect. After reading some documentation and other posts on similar topics, you can use a named query to cause EAGER fetching, but not to cause LAZY fetching.

So basically, my lesson is make everything lazy and use named queries when you need things fetched eagerly.