Steve, I will try and get back to you.
>losing alot of the value that something like NHib brings to the table for you Totally agree. In summary, we used NHib on our last big project and have a lot of performance problems. Mainly because NHib is deleting every item in a collection individually when its parent gets deleted, it updates every child when a parent gets updated, not using lazy loading across properties etc. NHib is throwing a lot of SQL at the DB that it really doesn't need to in our business content. These were all issues I inherited from the last architect who left. I actually like NHib and want to use it on our next big project but first I need to understand exactly how to make it perform and submit just the SQL what it needs to. Everything I'm doing is a process of getting NHib to submit the bare minimum SQL it needs - I'm getting there I think but, like you say, I feel some of the benefits of NHib are slipping away which doesn't seem quite right - I must be approaching things in the wrong way. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
