I am building a web based quoting system for a local automobile dealership.
I think I have figured out the logic for the databases but I want to get a second opinion before I start just to make sure I am doing it right.
I am working with the service plans for various vehicles and the client wants a drill down type search to find the required service plan e.g. Model of vehicle, transmission, etc...
The thing is the drill down is dynamic so some cars only have one type of transmission manual or automatic but with others you have to pick, the same applies to airbags and a few other things.
I was thinking I would have one table with the models and their specifications and then another table for each service plan at X number of KM's/Miles.
The table with models/specifications would populate the drop downs and I would then use this data to formulate a query to find the correct service plan table.
The reason for keeping the service plans in individual tables is because the data is so inconsistent.
Does this sound like the right approach?