I want to use EntLib 5.0 Data Application block in my SIlverlight 5+RIA application.
I want to maintain an Audit trail of user DB transactions. One idea is to customize DAAB so that each database insert/update/delete call besides making an entry in main table also makes an entry in audit table as well.
Jun 6, 2012 at 12:26 AM
Edited Jun 6, 2012 at 12:27 AM
Modifying the block would be one way to achieve auditing. Others ways that I've seen are:
- Write a facade around the DAAB to perform the requested action and audit it
- Database Triggers
on the methods/classes that perform database actions
- Event Sourcing appears that it is becoming a popular method to capture application state changes
Which one is best? As in most things it depends (e.g. existing application design, time, inclination, politics/standards, etc.).
Enterprise Library support engineer