Categories....

[Guest]

May have been requested already, but i did not see it. How about making some changes to the categories table. Instead of on table for the categories having multiple tables. Basically if i have 4 tiers in the categories table making each tier entry another table. Right now it is as follows in one table Domestic->Ford->Mustang->Suspension. I would drop down 3 tiers then have to get to the parts. why not make each of thse tiers a seperate table?

 

Yes I know it would add overhead to the database, but would it not make advanced searches a lot easier. of course I am no mySQL guru and never claim to be. I just had this thought.

[Guest]

That is actually very bad database design... The whole purpose of having a relational database is to get rid of redundant objects and make maintenance easier in the long run.

 

What if you decide to handle your parts list like: Domestic -> Year -> Ford -> Mustang -> Variant -> Engine -> Suspension. Especially since there are at least four different models of cars sold under the Mustang name and have different parts based on what was installed in the factory and each varies by year as well.

 

So now you have 7 tables and some of those tables are going to carry empty records which will take up space as well especially since cars like the GM Saturn didn't exist in 1980 whereas the Mustang started in 1965 (64 1/2 in reality) and other brands like Kia are newer still.

 

Keeping it all in one table and using a linked list methodology makes coding the system a lot easier, makes it easier to maintain, lowers the space requirements of the database and uses less resources making the system more robust in the long run.