> If I were you I would just use a single table with a > parent_id concept. > That is how we store our contact manager information. All > companies, departments, and contacts are all an "entity" and > they can be nested n levels deep. We have an entity table > with a type (contact, department, company etc.) and a > entity_id_parent column which points to the parent record. > Records with a NULL parent at top level. > > Depending on how many levels you have it can get tricky to > figure out ancestor or descendant relationships, but > recursion lends itself nicely to this kind of data. The best > part is it has no restrictions.
You might also consider using the nested set model for this, instead of an adjacency list model (the "parent_id" concept). Google "nested set model" for more information. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! This email has been processed by SmoothZap - www.smoothwall.net ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJQ Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:280432 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
