I've actually had an opportunity to think about this problem recently. In my case I decided to store the individual events because we would never have that many (< 1000 total events/year), and we wanted the ability to customize the description for each of the recurring events.

Are your users going to be benign? Do you have to handle events that recur indefinitely or can you put a limit on the number of recurrences? If you can prevent abuse, I would initially go with storing it. Save a "recurrence group id" with each event so you can get at all of the other events in the same sequence.

It will certainly be the easier route. You can always make it more sophisticated later.

In reply to Re: precalculating event dates vs.recalculating them. by pc88mxer
in thread precalculating event dates vs.recalculating them. 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.