Hey Folks,
I have an auditing requirement (journaling) for a web project. To address this, I went ahead and implemented auditing in my project using DI similar to the Auditing Example - Adapter Sample but instead of auditing the CustomerEntity (via the DatabaseAuditor class) I set it up to Audit all the Entities. I did this by setting the DependencyInjectionInfo attribute to audit all entities in the project and uncommenting the code in AuditLoadOfEntity() and AuditEntityFieldGet(). Doing this yields a ridiculous amount of rows in the AuditInfo table. Holy Cow!!! I'm thinking this is because it's auditing all the dependent entities as well.
I'm not interested in auditing the loading of existing dependent entites so I'm wondering if instead I should audit only on specific entities. If I were to take this approach would I need to implement a specific auditing class for each audit entity? In other words would I need to add the DI class attribute code to each of the entities I wish to audit or is it possible to specify which classes I wish to audit w/in the config file or maybe some other way?
I was wondering if any of you folks had a suggestion, perhaps there is a better way to handle this.
Thanks for your help. Btw, I really like the LLBLGen product. Great job!
Bob