Hi, When we implemented this sort of functionality previously our schema was something like this:
* non-recurring events * recurring events info * recurring exceptions We stored simple config information relating to the recurrence and any exceptions to this were flagged in the exception table. This way we didn't have to physically store an event for every recurrence, moreso generated this at runtime using the recurrence ranges, taking into account any exceptions. This kept the data storage requirement down to an absolute minimum important when scaled up to a couple of million users! Cheers, -Dan 2010/1/11 Calvin <[email protected]> > Hi, > > Hope this can help you to get some ideas: > http://martinfowler.com/apsupp/recurring.pdf > > Also look at this too: > http://stackoverflow.com/questions/85699/whats-the-best-way-to-model-recurring-events-in-a-calendar-application > > Calvin > > > > On 11/01/2010, at 11:35 AM, .Net2Php wrote: > > Does anyone have any suggestions on how I can represent singular/ >> recurring events in a database? I'm looking for a solution that would >> allow me to support an interface similar to Outlook's event scheduler. >> I think it may be iCal compliant. >> -- >> NZ PHP Users Group: http://groups.google.com/group/nzphpug >> To post, send email to [email protected] >> To unsubscribe, send email to >> [email protected]<nzphpug%[email protected]> >> > > > -- > NZ PHP Users Group: http://groups.google.com/group/nzphpug > To post, send email to [email protected] > To unsubscribe, send email to > [email protected]<nzphpug%[email protected]> >
-- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected]
