I would have (at least) four tables in my database:
  1. The table with all events (recurring and not recurring)
  2. The table with all dates on which an event will take place
  3. A linking table between the "event" table and the "date" table.
  4. The table with the formula for recurring events.

Every so often (say once a week for all future events and immediately once a new recurring event is entered) the table with recurring events is read and the dates for these events (or only for the new recurring event -- as the case may be) for the next x months are calculated and put in the dates-table and linking table. At the same time, past events are deleted from all tables as necessary.

I find this a good balance between fast look-up and keeping your tables simple, lean and easy to maintain.

CountZero

"If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law


In reply to Re: storing and 'understanding' complex calendar events (including recurring events) by CountZero
in thread storing and 'understanding' complex calendar events (including recurring events) by schweini

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.