I have Object Rubric that has an 1:n mapping to itself.
When defining this mapping as lazy this will end in the n+1 Problem.
When defining this mapping non lazy, my whole tree is loaded (m selects to the database)
Regarding performance both of these possibilities ar bad.

Is it possible to configure the load depth per session?

Is there another way to load all the sub-rubrics at once, but not the sub-sub-rubrics?





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

[b]Hibernate version: 3[/b]

[b]Mapping documents:[/b]

[b]Code between sessionFactory.openSession() and session.close():[/b]

[b]Full stack trace of any exception that occurs:[/b]

[b]Name and version of the database you are using:[/b]

[b]The generated SQL (show_sql=true):[/b]

[b]Debug level Hibernate log excerpt:[/b]

I am using the following approach in my applications:
1. Map almost all relations as lazy
2. When you need deep read (eager fetch in Hibernate terms;) use JOIN FETCH HQL construction