I am trying to simply load an entity, modify a property and then save it back to the database.
var db = new NewsletterContext();
var newsletter = db.Newsletters.Find(x => x.ID==newsletterID);
newsletter.SomeProperty = 5;
db.SaveChanges();
This causes a validation error as there are some properties on the newsletter object which are required and apparently not loaded when I do a Find()
.
I can solve this using an Include()
for each required property followed by a Where()
:
var db = new NewsletterContext();
var newsletter = db.Newsletters.Include(x => x.RequiredProp1)
.Include(x => x.RequiredProp2).Include(x => x.RequiredProp3)
.Where(x => x.ID==newsletterID)
.FirstOrDefault();
db.SaveChanges();
This isn't a very elegant solution and will break if I add more required properties to the Newsletter
object.
Is there a better solution?
Do not want to pollute your model with foriegn keys? Good! Read on. Instead you can override the
SaveChanges
method inNewsletterContext
. Get all modified entities and using reflection, load all their lazy loaded properties and collections using the following sample syntax:It won't be easy as it sounds, but once you are have written it, it would feel so good to see it work seamlessly :)
Entity framework will disable lazy loading when doing the validation. Hence if you put required validation on navigational properties the validation will fail. You can decorate the scalar property related to the navigational property instead.