See below for type two
“player_pship” (player partnership) is normalized from the player and partnership table.
·
I implemented this for fear of problems such as:
Searching for total statistics of either batter or bowler. The type 1 design
will need a search for every column of the partnership table whereas the type 2
design will search for the rows of the player_pship table.
· The “player_pship” table’s primary key is made up of p_id and pship_id.
· The is_batter attribute is a Boolean. A false represents a bowler.
· The p_number attribute is the index of the player in that partnership. A batter can have index of range (1-2). A bowler can have an index range of (1-8)
· Please let me know of any problems or suggestions.
I’ve change some of the entities to weak entity set for
better representation of the system.
For this design, the inning is a weak entity to game, the partnership is a weak
entity to inning, and the player_pship is a weak entity to partnership.