normalization - Is this database schema practical? -


as sort of follow previous question: normalizing variety of properties similar data types

i've created setup now: http://schemabank.com/p/vwwhn

my question on right path method? there obvious mistake setup i'm using, or concepts of normalization i'm missing? i'm trying go practical approach works in real world scenarios, if there better method configure database i'd happy hear it.

you might want have platforms_data table, allow associate game across more 1 platform. might conscious choice not have this, thought i'd mention it.

the other thing release dates, assume have separate release_dates table can select release date. if not part of plan, may not need table , include in game model.

another thing consider games released in different countries on different dates. since bringing multiple countries schema rating purposes, perhaps consider adding country table , removing country specific ratings tables. have single ratings table, each rating having country foreign key. have create ratings_data table associate games various ratings. use add country_id release_date_data table. approach allow expand , add more countries without having change schema every time.


Comments

Popular posts from this blog

asp.net - repeatedly call AddImageUrl(url) to assemble pdf document -

java - Android recognize cell phone with keyboard or not? -

iphone - How would you achieve a LED Scrolling effect? -