Do I understand you correctly that you based on X want to audit type Y? If so...
1. Turn on audit for Y on as usual. 2. Inherit AuditEventListener and override OnPostInsert, OnPostUpdate, OnPostDelete, OnPreUpdateCollection, OnPreRemoveCollection and OnPostRecreateCollection. In this method, look if X is fulfilled - if it is, call the base impl. If not, do nothing. Your AuditEventListener impl you pass into the IntegrationWithEnvers method. /Roger -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of vigj Sent: den 7 maj 2012 11:12 To: nhusers Subject: [nhusers] disable NHIBENATE ENVERS during batch operation I have sometimes long batch operations that populate a lot of record in tables. ENvers in this situation can have a big performance impact on transcation commit (the commit must write thousands of records + envers log info). Can Envers be disabled by code and then (after the long operation is completed) re-enabled again? -- 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. -- 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.
