It doesn't appear to be possible to lazy Load a component. I was thinking that I could simulate this with a Lazy one-to-one mapping. So I was wondering if it would be possible to map a one-to-one assosciation to the same table? There is an attribute named foreign-key that pops up in my schema intellisense for a one-to-one mapping but I can't find any documentation on this attribute. What is it used for?

have the same problem. I have entries in my database that store SOAP messages (> 100kb) and additional data about those messages. When I retrieve those entries, I don't want to load the XML data with each entry because it's a server app.

I read about the lightweight class pattern or so, where I use a base and a derived class, one w/o XML field and one with it. However, that sounds like overkill to me because right now I'd already have to do that for 10 domain classes, and still growing.

My question is if it is possible either with one-to-one or with a component to get a lazy load behavior. I read somewhere that if the linked class only has virtual properties, I can get proxy behavior. However, I couldn't find the place anymore and especially no instructions of how to do that.

If anybody could give us a hint, that's be reeeaaally great. Yeeaah!

Thanks, Christoph

Too the best of my knowledge componets can not be lazy-loded. They are data from the same table, but are broken out as a seperate class. The only way to hide data from a table in it's class is to not map it or use sub classing (inheritance).

I am interested to see if you tried this and had any success. It seems like it would be very useful for big BLOB columns (at least for reading).

I never got it to work and I am having the same problems with blob columns. I tried to set up a one to one relationship and have my blob as its own object but I cant get that to work either. See my posts in this thread:

http://nhibernate.sourceforge.net/forum/viewtopic.php?t=245

Blob columns are a major pain for me right now. All Im trying to do is come with a design that makes them even practical to use with NHibernate.

Hi jnapier,

I've responded to this issue in one of your other threads as it seemed more relevant there: http://nhibernate.sourceforge.net/forum/viewtopic.php?t=245

Cheers,

Symon