Let's say I'm modelling an organizational hierarchy which consists of Divisions that contain Departments that contain Teams. So Division -> Department -> Team.While it makes sense for the Division class to contain a collection of Departments, should the Department class contain its parent Division object or just the parent Division's identifier?I can see how having the parent object immediately available is convenient but I'm concerned about circular references.
Should I reference both up and down a hierarchy when using Entity Framework?
c#;entity framework;circular dependency