Zero work. http://fabiomaulo.blogspot.com/2009/10/nhibernatevalidator-nhibernate.html
<http://fabiomaulo.blogspot.com/2009/10/nhibernatevalidator-nhibernate.html>The serie http://fabiomaulo.blogspot.com/search/label/Validator On Wed, Aug 18, 2010 at 5:20 PM, MattO <[email protected]> wrote: > In my old data access layer I had my own Update method. This method > would perform the SQL necessary to update the object. It would also > do validation on the object before saving it to the database. > > For instance I have a rule that I can not update an entity if a > certain condition is invalid. The condition that I am checking > requires another call to the database before I save the record. > > I'm assuming I will either have to use the Interceptors and Event > system in nHibernate to capture all methods that could save a value to > the database (transaction commit, Flush, SaveOrUpdate, Save, Update, > etc). Is that true? If so seems like a lot of work since there are > so many methods I would have to capture to validate my entity before > persisting the changes to the database. > > -- > 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. > > -- 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.
