Question

I have for example, a DB with the following entity and relation structure:

[Person] has many [Skills], [Skills] has many [Actions]

In the .hbm.xml’s, I assign one-to-many relations for person > skills, skills > actions.

In a query, I would like to be able to control when I query on Person, to eager load only the Skills. Currently, I seem to be stuck where i’m eager loading NOTHING, and generating a n+1 amount of queries to get a Person’s Skills, or am generating an (n*n+1) amount of queries as it eagerly loads the entire Person > Skills > Actions collection hierarchy.

How would I limit it such that I can control when I do and do not want to load the third depth table? For context, I’d be able to live with always having Person > Skills collection initialized, ideally as a JOIN to prevent n+1 performance bottlenecks.

Answer 1

This turned out to be pretty easy to control at runtime.

In my .hbm.xml’s i continued to declare my association sets as lazy, (even extra lazy!).

In the HQL query, I query like:

Select distinct p from Person

left join fetch p.skills

the fetch keyword forces eager loading for that particular join.