title: one to many relationship in database - design concept
body: <p>A one to many relationship between two tables should be implemented with two or three tables?
  For example should we have:</p>
  
  <pre><code>author(id,otherAttributtes)
  books(id,authorid,otherAttributes)
  </code></pre>
  
  <p>or</p>
  
  <pre><code> author(id,otherAttributtes)
      books(id,otherAttributes)
      authorConnectsBooks(authorid,booksid)
  </code></pre>
  
  <p>I like more the first approach but i have seen the second and in more complicated applications a lot of times. Is there any downside for the first method, or it's just personal which way to follow?</p>