Database Design Help
[660 byte] By [pissa] at [2007-11-11 10:30:34] 
Hi, I am gonna be designing a database for some printer assemblies. Each of these assemblies have parts within them and there can be other assemblies inside of an assembly. I originally thought of making just one big table with all of the components, then just trying to weed through the the table, however I was wondering how I would flag each component. The other idea I had was to create a seperate table for every assembly and then just display all the contents of that table when needed. Now I know these are not the easiest way to design this database, and I was wondering if anyone could give me some suggestions on what would be a better way to design.
# 1 Re: Database Design Help
Would a parent/child/child relation do the trick? like 1 assembly to many assemblys within a assembly and that to a many parts? e.g. 1 to many to manyl_schuiling at 2007-11-11 23:43:19 >
# 2 Re: Database Design Help
Yes I think so. I was just doing some research on that. My only question now would be would I need to create a seperate field for each "parent" of the children?Printer
carriage > overflow >etcetc
Where the carriage > motor > wiring > nuts n bolts
Where the motor > wiring > nuts n bolts
Where the overflow > waste tank > wiring > etcetc
Now there is wiring definited in differen branchs of the tree. Is there a way to associate the wiring needed for each of these processes without getting redundant in creating all these additional fields.
pissa at 2007-11-11 23:44:16 >
