Hi

I have some objects with a great many properties, many of which are only occasionally needed.

Ideally, I would like some sort of lazy loading of the columns that are not needed, as it takes a long time to retrieve all columns for a large collection.

I know NHibernate doesn't support lazy loaded columns (shame!).

I have got the "component" working, which is great, but this doesn't seems to support lazy loading either (i.e. it would be nice if NHibernate could load all columns of a component and instantiate it when the component was accessed.

So, is the only way for me not to load all properties at once, to split my class into parts and set up one-to-one lazy relationships between the parts? This is going to be quite tedious, and make coding a little more complex.

In addition, my schema is such that a great many of the tables have the same sets of "little used" columns - more ideally suited to the component structure, I think?


Well, I would greatly appreciate thoughts on this issue.

Thanks,
Mark.

Hi!


You should read this: http://hibernate.bluemars.net/403.html



You have to do this manually, read this and this together with this from the manual.


No, you should not twist and bend you domain model to get hibernate to work properly for you. That would be bad OO. Hibernate embraces the POJO/POCO approaches for creating domain model classes.


Hope some of the links proved to be useful.
Cheers,
Steinar.

I read it. Nonethewiser. What have I missed?



Can't see how these help me lazily load components.



Totally agree, in theory.

In practice, I am trying to load a very large collection of objects with a very large number of properties. This is inefficient. I need to the core properties always, and only load some of the lesser used properties when they're needed.

Thanks anyhow,
Mark.

From my understanding a component is considered a part of the parent object and is completely tied to it's lifecycle, which includes loading. If you need lazy loading you should extend the associated objects to be full blown entities and use cascading to tie them to the lifecycle of the parent object.

Hope that helps.

Symon.