entity-framework-core

On this page of the Entity Framework Core documentation, it says when querying loaded data: Entity Framework Core will automatically fix-up navigation properties to any other entities that were previously loaded into the context instance. So even if you don't explicitly include the data for a navigation property, the property may still be populated if some or all of the related entities were previously loaded. This is true whether it is Eager or Explicit . I find this to be frustrating, because it will return partial data, which makes it seem like a complete list because there's nothing

I have designed my models so that it should not be created with a null parameter. For example, if I want to enforce that every Post should have a corresponding Blog , then my models will look like: public class Post { private Post() { } public Post(Blog blog) { Blog = blog ?? throw new ArgumentNullException(nameof(blog)); } public int PostId { get; private set; } public Blog Blog { get; private set; } } public class Blog { public int BlogId { get; private set; } } This way, it will throw an Exception if blog is null . But I use EF Core and it fails this test. public class Tests { [Fact] public

I am trying this activity to clone from existing .edmx project to code first. I have two entities. I want to have many to many relation without creating a new table. I am using EF Core 2.0 code first approach. Please find below the entity i have created. I am not sure whether is this is the right way to do this. I would like to have the foreign key column on both the tables ie. WorkflowId and WorkCaseId on WorkCase and Workflow tables respectively. public class WorkCase { [Key] public int WorkCaseId { get; set; } public int WorkflowId { get; set; } public int CaseDetailId {get;set;} public

I want to validate when certain Entity is Modified/Updated/Inserted/Deleted in Entity Framework (with database). (eg ProductType Entity table) ** Would like Change Tracker to be saved and queried later, as 'the track changes are lost if they are not saved before the DbContext object is destroyed.' Only need ChangeTracker to be retained for couple hours most to analyze, and be saved in MessageQueue if needed. MemoryCache can also work. 1) Someone recommend using LoggerFactory: optionsBuilder.UseLoggerFactory(loggerFactory) https://www.entityframeworktutorial.net/efcore/logging-in