You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment every entity inherits from AuditEntity and thus creates auditting.
To avoid massive obsolete audit records it is preferred to be able to configure which entity generates auditting.
1). Would you implement this in the boilerplate?
2). If not, how would you handle this? I was thinking that ApplicationDbContext.UpdateAuditProperties would need a cached list of the 'AuditSettings' records that were configured ( somewhere ), but how would you do this?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
At the moment every entity inherits from AuditEntity and thus creates auditting.
To avoid massive obsolete audit records it is preferred to be able to configure which entity generates auditting.
1). Would you implement this in the boilerplate?
2). If not, how would you handle this? I was thinking that ApplicationDbContext.UpdateAuditProperties would need a cached list of the 'AuditSettings' records that were configured ( somewhere ), but how would you do this?
Beta Was this translation helpful? Give feedback.
All reactions