Fetching strategies

MSchmidke · **Joined:** Wed Nov 02, 2005 4:03 am **Posts:** 7

Hibernate version: 3 / JBoss 4.0.3 / EJB3.0
Name and version of the database you are using: Oracle 9i

With EJB3.0 I've some problems with fetching strategies, because some things don't seem do be the same as with plain Hibernate (and work different than documented).

The docs say, all associations are lazy by default. However, in my configuration all to-one-associations seem to be eager by default. Why? Is this EJB3.0?

The docs say, eager associations are fetched by additional selects by default. However, in my configuration, all such associations are fetched in gigantic joins; if I don't manually tell some "lazys" to some to-one-associations, Hibernate selects nearly the entire database in one single join.

Criteria.setFechMode() does not seem to work at all. It neither gives errors for invalid paths (I've seen this is a bug which is open at least since Hibernate 2), nor has it any effect with correct paths.

Can you help me???

Thank you!

Marcus.

emmanuel · **Posted:** Wed Nov 02, 2005 7:04 am

Hi,
Point to me the Hibernate Entity Manager reference documentation mistakes or lacks and I'll fix them.

http://www.hibernate.org/hib_docs/entitymanager/reference/en/html_single/

landels · **Joined:** Thu Sep 01, 2005 8:43 am **Posts:** 14

Hi,

I was wondering - the EJB3.0 public draft specifies that OneToOne and ManyToOne associations are eagerly fetched per default.

On the other hand the Hibernate 3.1 reference states:

Quote:

By default, Hibernate3 uses lazy select fetching for collections and lazy proxy fetching for single-valued associations.
These defaults make sense for almost all associations in almost all applications.

So what is the case if one relies on the defaults... Must admit - I was lazy and never tried :)

cu,
landels