title: data model design pattern that holds data changes until authorized by another user
body: <p>Is there a design pattern to consider when building a data model for a banking application that requires data changes to go through an authorization level?</p>
  
  <p>For example, if admin1 changes the telephone number for customer1, the change should not be effective until admin2 authorizes it. </p>
  
  <p>The solution we plan to implement is to have a temp table to hold the changed record with the changed values and once the authorizer approves the change, then we update the main table. This works fine when you have few tables, but would be cumbersome as tables increase.</p>