Hi,
I have searched all over the forums and all over the web, both for NHibernate and Hibernate answers, but can't seem to answer this. I hope it's simple.
In our model, we have a concept of Entities and Activities. A single entity will have multiple activities. Every day new activities are added to an entity. The problem is that as time goes on, this list grows rather large to the point where in order to load a single Entity and add a new Activity, a list of 1000s of Activities has to be loaded first. Even with Lazy Loading turned on, the first reference to the collection to add a new Activity triggers the load which can cause delays.
What we are looking for is design guidelines when it comes to implementing objects that can potentially have large collections of children.
Thank you very much.
|