title: Database design - Multiple "Contact information" for different tables
body: <p>I have a database with tables "person", "company", "shop", etc. Many of these tables must have "contact information". The possibility to design this was asked in <a href="https://stackoverflow.com/questions/3636061/database-design-similar-contact-information-for-multiple-entities">Database design - Similar Contact Information for multiple entities</a>
  Now, in my database <strong>I leave a possibility to have a multiple addresses, multiple phones and multiple emails to each contact data</strong>. This is my database schema:</p>
  
  <p><img src="https://i.stack.imgur.com/iU2YT.png" alt="database contact information"></p>
  
  <p>So, <strong>I make an intermediate table "contact" as a simplest way to link a "contact information" to each table.</strong><br>
  <strong>My question: is it a good practice to do this and to have a table with only one row?</strong></p>