navigation-properties

I've got an EF hierarchy that (dramatically simplified) looks something like this: class Room { EntityCollection<Session> Sessions; } class Session { EntityCollection<Whiteboard> Whiteboards; EntityReference Room; } class Whiteboard { EntityCollection<WhiteboardShape> WhiteboardShapes; EntityReference Session; } abstract class WhiteboardShape { EntityReference Whiteboard; } class WhiteboardShapeEllipse : WhiteboardShape { } class WhiteboardShapePolyline { WhiteboardShape { EntityCollection<PolylinePoint> PolylinePoints } class PolylinePoint { EntityReference<WhiteboardShapePolyline>

When I use the .Include syntax in EF6, reverse navigation properties are always loaded. Is there a way to turn that off? Here is a sample query. private static IQueryable<Account> GetAccountsEager(this IRepository<Account> repository) { return repository .Queryable() .Include(e => e.AccountLocations .Select(l => l.Address.City.State.Country)); } This gives me the account's collection of AccountLocations. However, the Address' city has this reverse navigation property on it: public virtual ICollection<Address> Addresses { get; set; } ..thus it back-load all the reverse navigation addresses to

Let's make a case to explain my problem. MyTable1 +id +myTable2Id MyTable2 +id MyView1 +id +myTable2Id MyView1 exists in the case, from data from the MyTable1. Now i want to create a Navigation property from my EF6.1 Code first approach in my View to MyTable2. I know that it was possible from the database first approach, but is it also possible from the code-first approach and how? EDIT: I search some on internet, but due many meanings of the word View, it's very hard to find information on it. Also with the approaches in codes that i tried, i always get an error that the migration can't be

I've been using Entity Framework Profiler to test my data access in an MVC project and have come accross several pages where I'm making far more db queries than I need to because of N+1 problems. Here is a simple example to show my problem: var club = this.ActiveClub; // ActiveClub uses code similar to context.Clubs.First() var members = club.Members.ToList(); return View("MembersWithAddress", members); The view loops through Members and then follows a navigion property on each member to also show their address. Each of the address requests results in an extra db query. One way to solve this

I want to get all contact entities (including Person -> Employees) Contact |<- Person | |-> Employer | |<- Organization | |-> Employees Person and Organization inherits from Contact. When i use FirstOrDefault my employees and my employer entity were not loaded. public Contact GetContactById(int id) { var contact = GetContacts().FirstOrDefault(c => c.Id == id); return contact; } private IQueryable<Contact> GetContacts() { var contacts = _contextProvider.Context.Contacts .Include("Addresses"); return contacts; } That's my current workaround: public Contact GetContactById(int id) { var contact =

instead of talking let me talk with code: Dim Contact = Context.Contacts.Include("Phones") Dim phone = Contact.Phones(0) Contact.Remove(phone) How do I refresh the context now, canceling last relation deletion? I tried: Context.Refresh(RefreshMode.StoreWins, phone) 'Doesn't recover the relation Context.Refresh(RefreshMode.StoreWins, _ ObjectStateManager.GetObjectStateEntries(EntityState.Deleted)) the last one throws an InvalidOperationException: The element at index 0 in the collection of objects to refresh has a null EntityKey property value or is not attached to this ObjectStateManager.