EF Core returns null relations until direct access

by

The reason is explained in the Loading Related Data section of the EF Core documentation.

The first behavior is because EF Core currently does not support lazy loading, so normally you’ll get null for navigation properties until you specifically load them via eager or explicit loading. However, the Eager loading section contains the following:

Tip
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.

which explains why the navigation property is not null in the second case.

Now, I’m not sure which of the two behaviors do you want to fix, so will try to address both.

The first behavior can be “fixed” by using one of the currently available methods for loading related data, for instance eager loading:

var mutants = db.Mutants.Include(m => m.OriginalCode).ToList();

The second behavior is “by design” and cannot be controlled. If you want to avoid it, make sure to use fresh new DbContext instance just for executing a single query to retry the data needed.

Update: Starting with v2.1, EF Core supports Lazy Loading. However it’s not enabled by default, so in order to utilize it one should mark all navigation properties virtual, install Microsoft.EntityFrameworkCore.Proxies and enable it via UseLazyLoadingProxies call, or utilize Lazy-loading without proxies – both explained with examples in the EF Core documentation.

More Related Contents:

  1. Entity Framework Core 2.0.1 Eager Loading on all nested related entities
  2. Filtering on Include in EF Core
  3. Entity Framework – Include Multiple Levels of Properties
  4. Dynamically change connection string in Asp.Net Core
  5. .Net Core 3.0 possible object cycle was detected which is not supported
  6. navigation property should be virtual – not required in ef core?
  7. auto create database in Entity Framework Core
  8. Entity Framework Code First Lazy Loading
  9. How to add the same column to all entities in EF Core?
  10. Unable to create migrations after upgrading to ASP.NET Core 2.0
  11. How to unapply a migration in ASP.NET Core with EF Core
  12. How to store JSON in an entity field with EF Core?
  13. Is there an Entity Framework 7 Database-First POCO Generator?
  14. How can I call a SQL Stored Procedure using EntityFramework 7 and Asp.Net 5
  15. Azure Function, EF Core, Can’t load ComponentModel.Annotations 4.2.0.0
  16. Could not load file or assembly Microsoft.Extensions.DependencyInjection.Abstractions, Version=1.1.0.0
  17. loading a full hierarchy from a self referencing table with EntityFramework.Core
  18. Entity framework EF.Functions.Like vs string.Contains
  19. Avoid or control circular references in Entity Framework Core
  20. Entity Framework | Sequence contains more than one matching element
  21. Working with SQL views in Entity Framework Core
  22. Entity Framework core – Contains is case sensitive or case insensitive?
  23. ef core doesn’t use ASPNETCORE_ENVIRONMENT during update-database
  24. How to load navigation properties on an IdentityUser with UserManager
  25. How to create a password protected database?
  26. Implementing recursive property loading in EF Core
  27. How to set Identity Seed value in code-first?
  28. EF Core takes a lot of time, sometimes, to perform SELECT query
  29. How to resolve .net core build error NETDSDK1061 and warning MSB3277
  30. How to access DbContext in .NET 6 minimal API Program.cs

Leave a Comment