title: Entity relationship design - Converting diagram to database tables in one-to-many relationship
body: <p>I have a database entity relationship diagram with the following entities and their attributes:</p>
  
  <pre><code>Flight:
  Date (primary key)
  Num_available_seats
  
  Reservation:
  CustomerName
  CustomerPhone
  
  Seat:
  SeatNumber (primary key)
  </code></pre>
  
  <p>Reservation is the middle ground relationship between the <code>Flight</code> and the <code>Seat</code>. There is a one-to-many relationship between <code>Seat</code> and <code>Flight</code> (namely, one <code>Flight</code> can have many <code>Seat</code>s by way of <code>Reservation</code>).</p>
  
  <p>When breaking down these relationships into tables, because this is a one-to-many relationship, I know that <code>Seat</code> can consume <code>Reservation</code> so that there doesn't need to be a specific <code>Reservation</code> table in the database.</p>
  
  <p>However, my question is this... In the table for <code>Seat</code>, I know to put the primary keys of <code>Seat</code> and <code>Flight</code> (<code>SeatNumber</code> and <code>Date</code>), but do I also include the non-primary attributes of the <code>Reservation</code> relationship?</p>
  
  <p>Here are my two options I'm toying around with:</p>
  
  <pre><code>Seat(SeatNumber, Date)
  Seat(SeatNumber, Date, CustomerName, CustomerPhone)
  </code></pre>
  
  <p>Which one is correct? Thanks for the help!</p>