I have some entities with a lot of fields. I am interested in auditing only a subset of these fields since they change rarely and are of important to my application. Non-audited fields change frequently and are of less importance to the business model so I don't want them to trigger an audit trail. Currently I use fluent configuration to explicitly specify which fields I am being audited and Envers will store only these fields in the audit table. When I load an entity by revision, all omitted fields are set to null or default (which is by design I think). In my scenario I need non-audited fields to be set as well. I think this could be done in 2 ways:
1. Use current values stored in entity table, even though they don't have the same value when the revision was created 2. Store all fields in the audit table, but trigger an audit trail only when a subset of fields change. 2nd solution works better for me, since the historical data will be somehow more accurate. Is there a way to extend NHibernate Envers tot this? -- 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.
