I have a question:
What is best? Leaving all lazy asociations true?

I know that if a i have an association that i always need to load
with an object then it's a good thing to make the association non-lazy

But there's an incovienence if i make an association non-lazy:
in HQL querys. When i query some data using HQL i don't usually
need that extra select or join for the association.

Is there a way of toggling betwing lazy - non-lazy at runtime?

Thank you,
Christian Constantinescu.

You can override the fetch strategy using both the IQuery and ICriteria interface. See this section in the documentation:
http://www.hibernate.org/hib_docs/nhibe ... e-fetching

>> I know that if a i have an association that i always need to load with an object then it's a good thing to make the association non-lazy

I will reluctantly accept that you can be certain that for every unit of work you ever do on object A you will also access the associated object B. Even so, what's the downside of leaving object B lazy? I do not usually ask, "why make it lazy," but rather "why not?" I'm not sure if this is a "best practice" or not, but it's worked pretty well for me so far.