I have found the best performance is to create a separate object for the grid and move data from the NHibernate object to the grid object. Instead of using a grid hierarchy I put a second grid on the page to manage the child data and only get the child data after the user makes a selection of the parent. Of course the second grid also has its own data object.
Doing it like this there is no issue with proxies or sending too much unnecessary data to the web page. It keeps the web page leaner and more responsive. John Davidson On Mon, Mar 15, 2010 at 4:27 PM, Graham Bunce <[email protected]>wrote: > Sorry, too tired to read the full post and work out what's going on > for you but look at this thread that I raised with similar questions: > > > http://groups.google.com/group/nhusers/browse_thread/thread/fce0810bee14d5b3# > > A proxy will always be a proxy unless you force replace it (I think) > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<nhusers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
