title: Table structure for handling list of items
body: <p>The following scenario is to be implemented in a Relational Database.</p>
  
  <p>I have the following scenario:
  There's multiple users, all unique. Each user can belong to 1 or more "teams". Each team can have an unknown amount of users.</p>
  
  <p>So far i get that i should have a table with all the teams and another with all the users. 
  But regarding on how to store the teams the user belongs to, do i need a field for each team id he belongs to? Do i also need to establish a limit of how many teams he can be in or can it be dynamic with a limit? (How to store a list, which in other applications the limitations are the memory available).</p>
  
  <p>Ideally i would want a structure that would allow me to easily look up which Teams the user belongs to.</p>
  
  <p>There's also a similar problem in the Teams table, do i also need to define a limit of users in the team? Do i need a column for each user in the team in that case?</p>
  
  <p>Lastly, is this example something that should be avoided and i should be looking to struct it differently? If so please provide an example.</p>
  
  <p>I'm not looking for code examples, only examples on how to build the relations in these.</p>
  
  <p>Also accepting some recommendations for documentation that talks about which database struct types to use for each type of problem.</p>