title: Why is EF adding a collection of objects to a table that has no foreign keys?
body: <p>I am doing DB First Modeling and I have a table called List.Country. This table has no foreign keys of its own. it is just a PK, Name, and Code.</p>
  
  <p>When EF maps the table over however, it adds three Virtual ICollections of entities that have a foreign key to the List.Country table. </p>
  
  <p>Why is EF doing this? The Country entity should not care who uses it. It should only care about what it does itself. The Entities that have foreign keys to the Country table are correctly mapped with a country object in it.</p>
  
  <p>Why is EF mapping uneeded properties. This causes problems in Integration testing because I now have to account for those objects even though they have nothing to do with the country object itself.</p>