Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • Thanks for the idea. But even in near future, as much as we have thought from the business perspective, we do not need multi level hierarchy such as Companies => Regions => Branch etc. Only one level of hierarchy would do. Commented Oct 21, 2016 at 10:43
  • BTW by hierarchy table you mean a separate table with two columns such as (CompanyID, Level) right? Commented Oct 21, 2016 at 10:44
  • By hierarchy, I mean ParentCompanyID, ChildCompanyID. Every company has it's level, so LevelID should be in Company table. Maybe I'm not understanding the requirement. Commented Oct 21, 2016 at 11:17
  • Let me rephase my question, I'm looking for Employee - Supervisor Relationship but for Company i.e. Company - Branch. So I'll have only one level of hierarchy. So I'm trying to understand which is the better solution to implement this. Whether to add SupervisorID in same table or introduce a new table to hold the relationships. Commented Oct 21, 2016 at 18:21
  • 1
    Separate table is a better way to go in terms of scalability. Only you can decide if you will put SupervisorID in the same table or not. Commented Oct 26, 2016 at 6:33