title: Repeat Event Calendar based - Database Design
body: <p>I have got similar question to: <a href="https://stackoverflow.com/questions/2481937/how-to-best-handle-exception-to-repeating-calendar-events">How to best handle exception to repeating calendar events</a>.</p>
  
  <p>My questions is regarding the database design.</p>
  
  <p>I have some event running indefinitely however sometimes the end date is known. Lets say i am creating one event to take one medicine so i know when it is going to start but i don't know when it need to be stopped, it will depend on the progress and how the doctor advises.</p>
  
  <p>Now the interesting bit is, though i will be taking medicine everyday at particular time, for some day it can CHANGE (Time, Dose etc).</p>
  
  <p>So, i will have one table storing the medication name, dose, start date etc. </p>
  
  <p>Questions:
  1. Should there be physical record for each day [As its subject to change on particular date]. But there can be millions of record if we start to store for each date.</p>
  
  <ol start="2">
  <li><p>Alternatively, i can have exception for the date user is changing the details.</p></li>
  <li><p>Or i can create record for 6 months and when the time will get closer either user can increase or system will increase automatically if the event is still going.</p></li>
  </ol>
  
  <p>I wonder how Google calendar handles repeat indefinably.</p>
  
  <p>Your suggestion will be appreciated.</p>
  
  <p>Pankaj. </p>