Databases
StackOverflow2013
Postsdbo
POLong living Entity Framework context - best practice to avoid data integrity issues
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POLong living Entity Framework context - best practice to avoid data integrity issues
    primarykey
    data
    text
    <p>As a very rudimentary scenario, let's take these two operations:</p> <pre><code>UserManager.UpdateFirstName(int userId, string firstName) { User user = userRepository.GetById(userId); user.FirstName = firstName; userRepository.SaveChanges(); } InventoryManager.InsertOrder(Order newOrder) { orderRepository.Add(newOrder); orderRepository.SaveChanges(); } </code></pre> <p>I have only used EF in web projects and relied heavily on the stateless nature of the web. With every request I would get a fresh copy of the context injected into my business layer facade objects (services, managers, whatever you want to call them), all of the business managers sharing the same instance of the EF context. Currently I am working on a WPF project and I'm injecting the business managers and subsequently the repositories that they use directly into the View Model.</p> <p>Let's assume a user is on a complicated screen and his first button click calls the UpdateFirstName() method. Let's assume SaveChanges() fails for whatever reason. Their second button click will invoke the InsertOrder() method.</p> <p>On the web this is not an issue as the context for operation #2 is not related (new http request) to the context used by operation #1. On the desktop however, it's the same context across both actions. The issue arises in the fact that the user's first name has been modified and as such is tracked by the context. Even though the original SaveChanges() didn't take (say the db was not available at that time), the second operation calling SaveChanges() will not only insert the new order, it will also update the users first name. In just about every cause this is not desirable, as the user has long forgotten about their first action which failed anyway.</p> <p>This is obviously being a silly example, but I always tend to bump into these sort of scenarios where I wish I could just start fresh with a new context for every user action as opposed having a longer lived (for the life of the WPF window for example) context.</p> <p>How do you guys handle these situations?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USe36M3
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POLong living Entity Framework context - best practice to avoid data integrity issues
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POLong living Entity Framework context - best practice to avoid data integrity issues
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POLong living Entity Framework context - best practice to avoid data integrity issues
      1. USPHeiberg
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload