When you say its a performance problem for other users, do you mean they also want to access the collection, but its too large for them. Or is the code snippet/ChildCollectionCount too slow for them?
When you say its a performance problem for other users, do you mean they also want to access the collection, but its too large for them. Or is the code snippet/ChildCollectionCount too slow for them? If its the first case, then perhaps you need to do a similar solution for them - identify exactly what they need and provide methods that offer that facility.
Very late, but you can apply a filter on the collection IQuery q = nhSession. CreateFilter(Parent. ChildCollection, "select count(*)"); long countResult = q.UniqueResult(); this will not force an initialization of the collection but instead perform a single query to the db.
I would recommend a seperate query, rather than a domain relationship. Then you can use all sorts of optimisations.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.