title: Onetomany with parent database design
body: <p>Below is a database design which represents my problem(it is not my actual database design). For each city I need to know which restaurants, bars and hotels are available. I think the two designs speak for itself, but:</p>
  
  <p>First design: create one-to-many relations between city and restaurants, bars and hotels.</p>
  
  <p>Second design: only create an one-to-many relation between city and place.</p>
  
  <p>Which design would be best practice? The second design has less relations, but would I be able to get all the restaurants, bars and hotels for a city and there own data (property_x/y/z)?</p>
  
  <p><strong>Update: this question is going wrong, maybe my fault for not being clear.</strong></p>
  
  <ul>
  <li>the restaurant/bar/hotel classes are subclasses of "place" (in both
  designs). </li>
  <li>the restaurant/bar/hotel classes <strong>must</strong> have the parent "place"</li>
  <li>the restaurant/bar/hotel classes have there own specific data (property_X/Y/X)</li>
  </ul>
  
  <p><img src="https://i.stack.imgur.com/1owJH.png" alt="Database design"></p>