I had decided to make the GameInfo model based on how one of my previous employers did database modeling. However it probably doesn't make as much sense to have a one to one model that just stores data that could easily be on the Game model. The GamePrice model is fine because it is one to many, so it inherently cannot be a column on the Game model.
I had decided to make the GameInfo model based on how one of my previous employers did database modeling. However it probably doesn't make as much sense to have a one to one model that just stores data that could easily be on the Game model. The GamePrice model is fine because it is one to many, so it inherently cannot be a column on the Game model.