Given a table :
CAR --- id model_id condition fuel_id release_year
Since many cars would have the same
Model and same
Fuel, there are 1:N tables created.
Car objects can have the same
Should I create a
Year table and then a
year_id field into
Design-wise, it seems accurate, but it seems weird to create a
Year table containing a list of years.
Still, this is actually what I do for
Fuel : a table containing a list of fuels types.
When is it accurate to create a new 1:N table instead of a field ?