Databases
StackOverflow2013
Postsdbo
POEntity Framework 5 Updating a Record
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POEntity Framework 5 Updating a Record
    primarykey
    data
    text
    <p>I have been exploring different methods of editing/updating a record within Entity Framework 5 in an ASP.NET MVC3 environment, but so far none of them tick all of the boxes I need. I'll explain why.</p> <p>I have found three methods to which I'll mention the pros and cons:</p> <p><strong>Method 1 - Load original record, update each property</strong></p> <pre><code>var original = db.Users.Find(updatedUser.UserId); if (original != null) { original.BusinessEntityId = updatedUser.BusinessEntityId; original.Email = updatedUser.Email; original.EmployeeId = updatedUser.EmployeeId; original.Forename = updatedUser.Forename; original.Surname = updatedUser.Surname; original.Telephone = updatedUser.Telephone; original.Title = updatedUser.Title; original.Fax = updatedUser.Fax; original.ASPNetUserId = updatedUser.ASPNetUserId; db.SaveChanges(); } </code></pre> <p><em>Pros</em></p> <ul> <li>Can specify which properties change</li> <li>Views don't need to contain every property</li> </ul> <p><em>Cons</em></p> <ul> <li>2 x queries on database to load original then update it</li> </ul> <p><strong>Method 2 - Load original record, set changed values</strong></p> <pre><code>var original = db.Users.Find(updatedUser.UserId); if (original != null) { db.Entry(original).CurrentValues.SetValues(updatedUser); db.SaveChanges(); } </code></pre> <p><em>Pros</em></p> <ul> <li>Only modified properties are sent to database</li> </ul> <p><em>Cons</em></p> <ul> <li>Views need to contain every property</li> <li>2 x queries on database to load original then update it</li> </ul> <p><strong>Method 3 - Attach updated record and set state to EntityState.Modified</strong></p> <pre><code>db.Users.Attach(updatedUser); db.Entry(updatedUser).State = EntityState.Modified; db.SaveChanges(); </code></pre> <p><em>Pros</em></p> <ul> <li>1 x query on database to update</li> </ul> <p><em>Cons</em></p> <ul> <li>Can't specify which properties change</li> <li>Views must contain every property</li> </ul> <p><strong>Question</strong></p> <p>My question to you guys; is there a clean way that I can achieve this set of goals?</p> <ul> <li>Can specify which properties change</li> <li>Views don't need to contain every property (such as password!)</li> <li>1 x query on database to update</li> </ul> <p>I understand this is quite a minor thing to point out but I may be missing a simple solution to this. If not method one will prevail ;-)</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USStokedout
    1. USStokedout
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POEntity Framework 5 Updating a Record
      1. USKasper Cottaar
      1. VTFavorite
    2. VO
      singulars
      1. POEntity Framework 5 Updating a Record
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POEntity Framework 5 Updating a Record
      1. This table or related slice is empty.
      1. VTUpMod
    1. COUse ViewModels and a good mapping engine ? You get only "properties to update" to populate your view (and then to update). There's still will be the 2 queries for updating (get original + update it), but I wouldn't call this a "Con". If that's your only performance problem, you're an happy man ;)
      singulars
      1. POEntity Framework 5 Updating a Record
      1. USRaphaël Althaus
    2. COThanks @RaphaëlAlthaus, very valid point. I could do this, but I have to create CRUD operation for a number of tables so I'm looking for a method that can work with the model directly to save me creating n-1 ViewModel for each Model.
      singulars
      1. POEntity Framework 5 Updating a Record
      1. USStokedout
    3. COWell, in my current project (many entities too) we started with working on Models, thinking we would lose time working with ViewModels. We're now going to ViewModels, and with (not negligible) infrastructure work at start, it's far, far, far clearer and easier to maintain now. And more secure (no need to fear about malicious "hidden fields" or things like that)
      singulars
      1. POEntity Framework 5 Updating a Record
      1. USRaphaël Althaus
 

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