Until now, most of the "Persistenc Layer" methods are single method calls to the session or queries. This is mostly to decouple NHibernate types form the business logic and for testability. There shouldn't be any logic except as provided from NHibernate. The problem is, if I change all the SaveOrUpdate operations to Merge, I have to refactor the business logic. And if I find another solution, I have to move it back ... The audit log function should be as hidden as possible, it could even be removed, replaced ... The switch to Merge is very intrusive.
On 11 Nov., 17:02, "Fabio Maulo" <[EMAIL PROTECTED]> wrote: > 2008/11/11 Stefan Steinegger <[EMAIL PROTECTED]> > > > > > Yes, I remember, I already used Merge for some special purpose. This > > could be a major issue, because we would have to use Merge as the > > default storing method through the whole system, by avoiding the > > business logic to know too much about such details. I'll see when I > > try if it is acceptable. Thanks again. > > Take care to don't delegate so much responsibility to your Persistence Layer > (NH). > > -- > Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
