Need help with Hibernate? Read this first:
http://www.hibernate.org/ForumMailingli ... AskForHelp

Hibernate version:
3.1.x

Mapping documents:
generated from xdoclet

Code between sessionFactory.openSession() and session.close():

Full stack trace of any exception that occurs:

Name and version of the database you are using:
oracle 9i

The generated SQL (show_sql=true):

Debug level Hibernate log excerpt:

i'm trying to dynamically change the fetchMode, ie.. overriding the default mapping files lazy="false" to be true for some queries.

using the criteria API, there seems to be no magic combination that will have any effect on the default settings in the mapping files.

i have a Parent object with a list of Child objects

using:
session = sessionFactory.openSession();
Criteria sessionCriteria = criteria.getExecutableCriteria(session);
sessionCriteria.setFetchMode("child",FetchMode.SELECT);
return sessionCriteria.list();

setting the fetchmode to ANY of the available options seems to have NO effect stopping the child list from loading.

i've tried setFetchMod("Parent.child",FetchMode.SELECT);

even setFetchMod("foobar",FetchMode.SELECT) has no effect or even an error message.

has anyone got this to work? please help!

g

The problem is that list of children is being fully populated even though you don't want it to be? Most likely, that's caused by having a criterion referring to the child collection. If the query needs to load something to execute, then hibernate doesn't throw it away if you don't want it: it optimizes things so that the in-memory list stays in memory, even if you don't need it any more.

Also note the javadocs for FetchMode.SELECT, as I think you're using it to do the opposite of what it actually does:

If you want to force a lazy load, simply omit that line. Assuming that child isn't referred to anywhere else in the criteria, hibernate now knows that nothing cares about the child collection, so it will automatically be proxied. Your lineforces hiberante to eagerly load the collection (simply by referring to the collection in the criteria), and further, to use separate select statements to do that eager loading.

That's not true. There's a big typo in the JavaDoc for FetchMode.SELECT which reads 'Fetch eagerly, using a separate select. Equivalent to fetch="select".'

It should be 'Fetch lazily, ...' It doesn't fetch associations; you'll get a lazyInitializationError.