title: Add a column or create a new table when updating a domain (DB) entity?
body: <p>In my database I have a table called Person with rows for ID and name and this works fine for the time being. Later on, after deployment, I realized I want a Person to also have an address (a single address per person). What is the best way to do this? Update the table with a new column for the address or create a new table Address for the address and link the two tables with a reference? Or, maybe, I should have one table Person, one table Address, and one table PersonAddressRelation with keys for both. </p>
  
  <p>I know a bit about table normalization. My question is: how to build a set a tables if you predict they might change?</p>