Is this database schema practical?

Question

To continue this previous question: Normalize various properties with similar data types.

I created this setting now: http://schemabank.com/p/VwWHn

My question is: am I on the right track with this method? Is there a clear error in the setup I'm using, or something about the normalization concepts that I skip? I am trying to find a practical approach that works in real-world scenarios, so if there is a better way to set up this database, I would be happy to hear that.

Answer 1

You might want to have a platform_data table that allows you to link the game on multiple platforms. It may be a conscious choice not to have it, but I thought I mentioned it.

Another thing is that for release dates, I assume that you have a separate release_data table so that you can select everything by release date. If this is not part of your plan, you may not need an extra table, and you can simply include it in the game.

, . , , . , . rating_data, . country_id release_date_data. .

Answer 2

:

• RatingsByCountry
• GameRatingsByCountry

, , .