In general, I understand that normalization is usually beneficial even with the join costs. However, I came up with an interesting dilemma recently.
What if the data is duplicated but unlikely to ever change. It's possible, but I would not anticipate it.
I have a
nutrients table with a
unit column and the units would be
I can't see these values every changing.
I'm tempted to just put them as a column in the table rather than normalizing and having a
units table and using a foreign key and having to join whenever fetching a row from the
nutrients table. At the same time, I know in general, even with the join coins, we should normalize.
What should I do (and why)?