Recursive Database Design Question

[LLudden]

The goal of the database is to be able to choose a manufactured item, and list all the components needed to make it. Some of the components themselves are manufactured from lesser components. There can be many sub components in any given piece.

Using an automobile for an example: Car consists of frame+engine+body

frame=electrical+brakes+drive train
engine=carburator+pistons+water pump+belts
body=<differnt pieces of sheet metal>

Drive Train=gears + axels

etc

What I am thinking of doing is storing each item in a table, with its name, and whether its a base item (tire), or a constructed item. If constructed, have a 2nd table that lists all the components needed for that item (Identity would be Final product key+component key).

Any thoughts on this before I get into the nitty gritty?

 

[codestorm]

I imagine you'd have two tables - one which contains every component, whether atomic or constructed, and another which would contain links between two components in the first table. codestorm
Fire bad. Tree pretty. - Buffy
select * from population where talent > 'average'
<insert witticism here>