Home/ Questions/Q 573409
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T13:43:15+00:00

For a clean data model, I’m going back and forth on this… Using an

  • 0

For a clean data model, I’m going back and forth on this…

Using an approval workflow as an example, let’s say in my web application I have a page that lets a user flag a MyEntityObject for approval. MyEntityObject has a few properties that control its approval workflow, so I have a common utility method out there called FlagForApproval(MyEntityObject eo).

Should the page call FlagForApproval() to set necessary properties only and then call SaveChanges() when it’s ready, or should FlagForApproval() save the changes?

Having the utility method save changes seems like it’s doing a little more than it’s asked to do (what if it was just one step in a series of operations?), but at the same time, making the page call SaveChanges() and commit the data to the DB seems like it could be considered too close to data layer responsibilities.

Thoughts?

(Update: FWIW, so far I have been having utility methods call SaveChanges(), that way the page only has one set of exceptions to handle, whether validation or data.)

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    My current opinion on this issue is to always have the business logic layer call save changes after validating data. When the user clicks Save button, i pass whatever entities need to be validated down to the BLL, and it decides whether to SaveChanges().

    I’m as curious as you though, to see what others say because this issue (and many other) has been plaguing me since i started with EF.

    • 0