0
I have a table in the database called Veiculo
and it has the following fields: placa
, renavam
, marca
, cor
and categoria
.
To the placa
and renavam
is all right, since the data are unique.
My question is about the columns marca
, cor
and categoria
. Today save everything on the table Veiculo
and do not relate to other tables. It is necessary and/or recommended, through "good practices", to create a table for marca
, another to cor
and another to categoria
and only refer to the respective ID
on the table Veiculo
?
The database behaves better this way, avoiding repeated information?
Possible duplicate of What is database normalization?
– Ismael
And one here It can be considered a bad modeling practice to store all people (customers, employees, suppliers) in the same table?
– Ismael
Or even this one: https://answall.com/questions/22069/quando%C3%A9-interesting-denormalize-the-database
– perozzo
Possible duplicate of When it is interesting to denormalize the database?
– perozzo