H
Hazz
I have been asked what I thought would be a good database design, data
delivery mechanism and rendering method for an org chart with as many as
100,000 people. No other design specifications.
1. Database design? Good question.
Employee Table
EmployeeID
EmployeeName
ParentNode (BossID ??)
Depth(some way to tell what depth the node is at)
???
2. Delivery mechanism? Dataset? anything better?
3 Rendering? Treeview control? GDI+?
What stymied me originally with this question is that there are various ways
to answer this but given the basic ideas above, are there any gems or wisdom
gained by anyone having done this? I am thinking about elegant and simple
database designs that just flat out work. Also any caching ideas to facility
quick navigation through an org chart (or any binary tree)? Does the
Treeview work well in asp.net? Any methods need to be overridden to enrich
that control? Any special sql queries to get back from the database only as
much data as will be used without getting everything. Does it matter?
Thank you, -greg
delivery mechanism and rendering method for an org chart with as many as
100,000 people. No other design specifications.
1. Database design? Good question.
Employee Table
EmployeeID
EmployeeName
ParentNode (BossID ??)
Depth(some way to tell what depth the node is at)
???
2. Delivery mechanism? Dataset? anything better?
3 Rendering? Treeview control? GDI+?
What stymied me originally with this question is that there are various ways
to answer this but given the basic ideas above, are there any gems or wisdom
gained by anyone having done this? I am thinking about elegant and simple
database designs that just flat out work. Also any caching ideas to facility
quick navigation through an org chart (or any binary tree)? Does the
Treeview work well in asp.net? Any methods need to be overridden to enrich
that control? Any special sql queries to get back from the database only as
much data as will be used without getting everything. Does it matter?
Thank you, -greg