New answers tagged normalization
2
First things that strike me are:
Your Movie table needs further Normalisation - holding lists of anything in a single field (actors) is a really Bad Idea.
You might want to have a "master" table of Genres and join it to Movies in an n:m relationship - a Movie can cross genre boundaries.
My suggestions would be to break out pen and paper and try ...
1
Is there a better design to store the data?
Probably. Considering the query constrains (no searches on measurement data and only retrieving full datasets), I decided to store the measurement data in a json field. Supported by MySQL and Laravel.
Are this many columns even that bad, if they are never searched?
Here I still don't have a concrete answer, but I ...
3
Is there a better design to store the data?
Probably. A measurement seems to be an entity in itself, and should be modelled like one. You will then need a one-to-many (or many-to-many, if a particular measurement applies to more than one scenario) relationship between scenarios and measurements.
Top 50 recent answers are included
