Best way to develop/manage/design recurring tasks/calendar

Question

An example of what I\'m talking about is similar to Google Calendar. When a new recurring task is created.

After creating the recurring task \"template\" - which all of

Answer 1

If the user requests a "month" view, and you want to display all of the events/tasks, it seems like creating the output in real time from the template, and including all of the exceptions would be a lot more resource intensive then if each individual recurring tasks was created from the template and inserted into the database.

I would disagree on that. What if a task repeats every saturday for the next 7 years... And what if there were a lot of these repeating tasks? That would cost you a lot of waste space. Therefor, I think it's better to save a recurring task as just one record + one record for every exception (since there are less exceptions than recurrences).

Well, the only problem left is how to set up a query to select each task (still thinking abou that)