I am moving a large existing app to NHibernate. There is a person class that is used throughout the application and needs to be performant. This class has a handful of properties (think things like resume) which are large chunks of text that are used in just a handful of instances. However, because NH mapping includes them, contents of these fields are always loaded and this is quantifiably affecting the performance of the app.

Is there a way to lazy load properties? If not, any other ways to handle this?

Thanks!
-MT

Do you mean that mapping the Person class as lazy="true" does not help, or didn't you use this option so far?

My understanding is that mapping Person as lazy would make references to the person object lazy. What is need is to have references to *properties* of the object to behave lazy. So that in 99% of the cases certain fields will not get pulled in and saved but when I reference them, a call will be made to get the data.

Hope that made sense.

-MT

P.S. Can a class be extended w/o using a discriminator? In other words, if I were to have a SimplePerson and an inheriting Person with a handful or extra fields, would that achieve what I'm after?

I'm not sure if this works, but it's worth a shot:

What about components?

Make the large text columns components using a separate class, and mark those as lazy. With components they still map to the same table, but they are separate classes.

If this doesn't work then I'd avoid using NHibernate for the resume portion and just roll my own ADO code for that one, using lazy loading. Sucks, but it's better than fetching all that data every time.