EF Code First not returning related objects

Question

I'm using EF Code First with a pre-existing database.

Two objects:

public Foo { public int FooId {get;set;} } public Bar { public int BarId {get;set;} public virtual Foo Foo {get;set;} }

Both FooId and BarId are primary keys in the database, and the Bar table has a column FooId which is a foreign key pointing at the Foo table.

When I select a Bar, Foo is a null reference. I would have thought EF would have automatically pulled the two of them together, but perhaps I'm missing something?

Database mappings:

public class EFCodeFirst : DbContext { public EFCodeFirst() { this.Database.Connection.ConnectionString = ConfigurationManager.ConnectionStrings["AlternateString"].ConnectionString; } public DBSet<Foo> Foos {get;set;} public DBSet<Bar> Bars {get;set;} protected override void OnModelCreating(System.Data.Entity.ModelConfiguration.ModelBuilder modelBuilder) { modelBuilder.IncludeMetadataInDatabase = false; modelBuilder.Entity<Foo>().MapSingleType().ToTable("Foo"); modelBuilder.Entity<Bar>().MapSingleType().ToTable("Bar"); } }

Can you also post your code first mapping? What happens if you call the query with Include("Foo")? — Ladislav Mrnka
– Ladislav Mrnka, Commented Nov 19, 2010 at 10:46

Morteza Manavi · Accepted Answer · 2010-11-20 04:04:35Z

If your expectation of Foo should not be null is coming from the fact that you make it virtual on Bar object, then that's not the case. By make them virtual, you just opt in to EF lazy loading and it will be null up until to the point that you explicitly ask for it by accessing it on Bar object. Other than that, if you want it to be populated upfront you would have to eager load it with Include method.

To explicitly disable lazy loading you can use the following code, even though you don't need it since you can just remove the virtual keyword from your navigation properties and lazy loading would be gone.

public EFCodeFirst() { this.ObjectContext.ContextOptions.LazyLoadingEnabled = false; }

Internally, DbContext uses a protected ObjectContext that you can also use inside your inherited DbContext class (e.g. EFCodeFirst).

But either way it should still resolve, correct? Either with an early or later call to the DB.
I also cannot figure when to disable lazy loading. None of the objects have a reference to ContextOptions.LazyLoadingEnabled.
Yes that is correct and it does work. You need to show us the code that does not work.
I also edit my answer to show how to change the value of ContextOptions.LazyLoadingEnabled

Shiraz Bhaiji · Accepted Answer · 2010-11-19 09:41:29Z

0

You are missing a line in the Foo class, that Foo contains a collection of Bar.

answered Nov 19, 2010 at 9:41

Shiraz Bhaiji

65.7k37 gold badges149 silver badges260 bronze badges

2 Comments

mattdwen Over a year ago

There is currently no need to access the Bar objects from the parent Foo.

Shiraz Bhaiji Over a year ago

Yes, but that is what tells EF to make the relationship, not having it gives you the null reference exception

Collectives™ on Stack Overflow

EF Code First not returning related objects

2 Answers 2

4 Comments

2 Comments

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

4 Comments

2 Comments

Related