This table will be the reference that ties your TeamPokemons together as a, well, Team.
A Team should / can have:
- A
name attribute which is a string. Users may want easier ways of identifying their team.
- A
game_id reference to a future Game class. We want to tie a specific Team to a specific Game so users know which game they used the Team in. This would be a 1:Many relationship since a Game can have multiple Teams but a Team can only belong to one Game. There is a possibility this should be allowed to be nil, in case the Game the user used the Team in doesn't exist in our DB. I'm mainly considering RomHacks like Ultra Shiny Gold Sigma, Reborn, etc. Those could also be added to the DB!
- Potentially a
rating attribute which would be an integer. Users may want to rate how much they liked the team / how well it performed. This would likely be 0-5, 0-10, or 0-100 scaling.
- Potentially a
description attribute which would be text. Users may want to write up a description of what the team is, how it is supposed to function, etc.
This table will be the reference that ties your
TeamPokemonstogether as a, well,Team.A
Teamshould / can have:nameattribute which is a string. Users may want easier ways of identifying their team.game_idreference to a futureGameclass. We want to tie a specificTeamto a specificGameso users know which game they used theTeamin. This would be a 1:Many relationship since aGamecan have multipleTeamsbut aTeamcan only belong to oneGame. There is a possibility this should be allowed to benil, in case theGamethe user used theTeamin doesn't exist in our DB. I'm mainly considering RomHacks like Ultra Shiny Gold Sigma, Reborn, etc. Those could also be added to the DB!ratingattribute which would be an integer. Users may want to rate how much they liked the team / how well it performed. This would likely be 0-5, 0-10, or 0-100 scaling.descriptionattribute which would be text. Users may want to write up a description of what the team is, how it is supposed to function, etc.