title: Multiple SaveChanges calls in entity framework
body: <p>I am building my own custom repository, based on entity framework, and I'm creating some extension methods that allow me to save partial view models as entity models so I'm building my own Add and Update methods.</p>
  
  <p>Currently, each method has SaveChanges() from DbContext called at the end which means for every model, one call will be invoked.</p>
  
  <p>I'm building this base DAL pattern for MVC4 sites which means most of the time I will access 1 model, but it does not have to be the case though.</p>
  
  <p>Is it too bad practice to call SaveChanges() for each model when updating i.e. 3 entities or should I add everything first to object context and than do SaveChanges() as some sort of transaction commit?</p>