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.

Reply via email to