title: Which is the better way of relating these database tables?
body: <p>I have a table <code>Users</code> and <code>Matters</code>. Ordinarily only admins can create a matter so I did a one to many relationship between users and matters(User.hasMany(Matter)) and (Matter.belongsTo(User))</p>
  
  <p>Now on the frontend, <code>Matter</code> is supposed to have a multi-select field called <code>assignees</code> where users gotten from the <code>User</code> table can be selected.</p>
  
  <p>My current approach is to make <code>assignees</code> a column on <code>Matter</code> which will be an array of user emails selected on the frontend but the frontend developer thinks I should make it an array of user ids instead but I think that won't be efficient because when getting all matters or updating them, one will need to run a query each time to get the associated assignees using the array of ids stored in the <code>assignees</code> column(and I am not entirely sure on how to go about that).</p>
  
  <p>Another option is having a <code>UserMatters</code> join table but I don't think it will be performant-friendly to populate two tables(Matter and UserMatters) on creation of a matter while updating and getting all matters will involve writing lots of code.</p>
  
  <p>My question is, is there a better way to go about this or should I just stick with populating the assignees field with user emails since it looks like a better approach as far as I can see?</p>
  
  <p><strong>N.B: I am using sequelize(postgres)</strong>  </p>