Re: vehicle to autoparts relationships
Date: 7 Dec 2006 09:24:06 -0800
Message-ID: <1165512245.975431.81320_at_j44g2000cwa.googlegroups.com>
> First of all, thanks for all of the input. I have to say I don't agree
> that all sectios of the automobile are parts and more than the vehicle
> itself is a part. Perhaps in real life, the consumer will but a 2000
> Ford Escort, and later may purchase a head gasket for it, so to that
> customer each one is simply a part# on his invoice.
While different, thinking of sections as parts, allows fewer tables. You could thinks in terms of things. Some things are sections and some things are parts (use attributes to distinguish). And these things have a parent/child or BOM-type relationships.
> In regards to my current database, I have a Vehicle table, an
> EngineConfiguration table, a Transmission table, and a host of others.
At extremes, there are two type of solutions to your problem in RMDBs. One solutions ends up with many specialized tables. The other solution ends up with fewer generalized tables with recursive joins. Each has advantages and disadvantages. You will have to find the right balance for your specific requirements. Received on Thu Dec 07 2006 - 18:24:06 CET