At this moment, Player_Caught_Player, Player_Found_Player, and Notification_Player have relations with the Player table. However, the actions that these tables represent (Notifying, catching, and finding) all happen within the context of a game. Therefore, these relations should point at Game_Player, istead of Player.
At this moment, Player_Caught_Player, Player_Found_Player, and Notification_Player have relations with the Player table. However, the actions that these tables represent (Notifying, catching, and finding) all happen within the context of a game. Therefore, these relations should point at Game_Player, istead of Player.
Burathar
added this to the Release 1.0 milestone 4 years ago
Replace PlayerId in Notification_Player with Game_Player_Id
Replace PlayerId in Player_Found_Objective with Game_Player_Id
Replace CatchingPlayerId in Player_Caught_Player with Game_Player_Id
Replace CaughtPlayerId in Player_Caught_Player with Game_Player_Id
Make clear in diagram that Game_PlayerRole defaults (to Role.none)
The names of the associationtables were not changed, because for instance Notification_Game_Player could be confused for a theeway association between Notigication, Game, and Player. Furthermore, The Player table is renamed to User, so Player only references Game_Player
Changes:
* `Player` table renamed to `User`
* Add Id to `Game_Player`
* Replace `PlayerId` in `Notification_Player` with `Game_Player_Id`
* Replace `PlayerId` in `Player_Found_Objective` with `Game_Player_Id`
* Replace `CatchingPlayerId` in `Player_Caught_Player` with `Game_Player_Id`
* Replace `CaughtPlayerId` in `Player_Caught_Player` with `Game_Player_Id`
* Make clear in diagram that `Game_Player` `Role` defaults (to Role.none)
The names of the associationtables were not changed, because for instance `Notification_Game_Player` could be confused for a theeway association between Notigication, Game, and Player. Furthermore, The Player table is renamed to User, so Player only references Game_Player
At this moment, Player_Caught_Player, Player_Found_Player, and Notification_Player have relations with the Player table. However, the actions that these tables represent (Notifying, catching, and finding) all happen within the context of a game. Therefore, these relations should point at Game_Player, istead of Player.
Changes:
Player
table renamed toUser
Add Id to
Game_Player
Replace
PlayerId
inNotification_Player
withGame_Player_Id
Replace
PlayerId
inPlayer_Found_Objective
withGame_Player_Id
Replace
CatchingPlayerId
inPlayer_Caught_Player
withGame_Player_Id
Replace
CaughtPlayerId
inPlayer_Caught_Player
withGame_Player_Id
Make clear in diagram that
Game_Player
Role
defaults (to Role.none)The names of the associationtables were not changed, because for instance
Notification_Game_Player
could be confused for a theeway association between Notigication, Game, and Player. Furthermore, The Player table is renamed to User, so Player only references Game_PlayerSolved in commit
b57d91d37c