Updating your computer is almost Best sex chat site ratings
Its probably better to do this with view models, though, in order to avoid repeating sets of properties.
I haven't done that yet because I don't know how to avoid bringing the validation messages on my view model validators into my domain project.
Instead of setting the entire object to "modified", it sets a set of individual properties.
(T is a class generic parameter.) I like one trip to the database.
If that's your only performance problem, you're an happy man ;)Thanks @Raphaël Althaus, very valid point.
We're now going to View Models, and with (not negligible) infrastructure work at start, it's far, far, far clearer and easier to maintain now.
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".
You won't receive an error because those fields won't be in your form.
You leave out the fields you will definitely not be updating, grab the entry from the database using the form passed back by attaching it, and tell the entry that those fields aren't being modified.