title: Database Time Availability Representation
body: <p>I'm just starting a project where I need to track employee availability.  Essentially each day is split into 5 periods and an employee may be available or unavailable for any period. In theory their availability may look like:</p>
  <p>Mon1 - False</p>
  <p>Mon2 - True</p>
  <p>Mon3 - False</p>
  <p>And so on.</p>
  <p>I'm attempting to create a model that will handle this efficiently.  Is it better to make it more generic or have one row with all availability?</p>
  <p>Option 1:</p>
  <p>EmpFK | Day | Period | Availability</p>
  <p>Option 2:</p>
  <p>EmpFK | Mon1 | Mon2 | .... | Fri5</p>
  <p>Either way it would be 25 rows or 25 columns which I feel seems overkill. Is there a more efficient way to represent this?</p>