Normalization

[programmer79]

Here is the revised structure of a database that I have been designing. I just wanted to know if (from a normalization standpoint) it is a solid structure. I appreciate any advice given.

Thank you,

Tony

http://www.expertcellular.com/car_table_revised.doc

[tasistro]

file looks empty, used open office to view it though. could that be it?

[Ravenous]

I was able to open it with MS Word, but not OO. As far as the table(s) go, it looks good to me, but, then again, I'm not an uber-SQL guy.

[superwormy]

Looks good, is there going to be a time when you want more than one image to go with the vehicle? It seems to me that might happen, so you might want to have another table for images.

Image

image_ID
vehicle_ID
image

Also, most of the time you dont' see tablename_ID as the primary key, most of the time you just see ID, for the reason that, when refering to a table and field, usually it makes just as much sense to type: vehicle.ID, than it does to type vehicle.vehicle_ID. The second is just kinda redundent.

But, of course, its up to you, not us, cause its your application :-)

[mattr]

You don't need the vehicle_feature_id -- the combination of vechicle_id and feature_id is the best primary key.