Ted Roche <> wrote:
>>> I was thinking of doing it in 1 table where sub codes link back to
>>> the parent. Are there other, better ways to do this? This allows
>>> some flexibility I belive, such as adding new levels if needed, but
>>> it also might be kind of slow to parse a given code.
>
> Self-joined tables make sense when all elements are the same thing:
> employees and managers and supervisors can all be in teh person
> table, with a hierarchical self-join.
>
> This system sounds more like a system-module-item hierarchy, and I'd
> favor three tables:
>
> System: pk, name, etc.
> Module: pk, systemfk, name, etc.
> Item: pk, modulefk, name, etc.
It's more like a list / lookup with a column for the final data value. I
see a BOM style sytem.
But YMMV.
Stephen Russell
DBA / .Net Developer
Memphis TN 38115
901.246-0159
"A good way to judge people is by observing how they treat those who
can do them absolutely no good." ---Unknown
http://spaces.msn.com/members/srussell/
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.441 / Virus Database: 268.18.3/699 - Release Date: 2/23/2007
1:26 PM
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
