Our company did not properly design Address Record Code Module. Developers are updating
Address SQL table with Multiple Service Methods, and are not updating
AddressHistory Sql table. They're asking me to unify/resolve the issue :) . What are some methods to resolve this?
I came up with these 3 alternatives. Just curious if there are anymore anyone can think of?
1) Create a common Repository function which updates Address History? Ask everyone to utilize this and app this to their code?
2) Should I create an IAuditable Interface that will intercept DB
SaveChanges and update Address History?
3) Utilize SQL Triggers (Sql temporal tables do not apply history changes in a customized manner)
Currently applying Net Core 2, Entity Framework, and SQL server