Populating all events also lets users delete/move individual events within the recurrence if they need too.
On Mon, Jan 11, 2010 at 12:05 PM, Warren Boyd <[email protected]> wrote: > On 11/Jan/2010, at 11:35 , .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. > > I've been doing some work on using EWS to talk to exchange (not quite > Outlook) - but if you have a look over the XML structure for EWS Calendar > items (http://msdn.microsoft.com/en-us/library/aa564765.aspx) this may > provide you some more input for what you are looking at. > > Without a lot of thought into how you want to do things (i.e. you may want > to provide detail to an interface that the item is recurring and how, as > opposed to flagging an item in a database as recurring, but populate all the > items) - I would probably tend to populate all the items in the database > based upon the recurring rules and have a recurrence flag along with a > unique ID to identify the "master". The advantage to that is that when you > retrieve items, you don't need to calculate the rules for recurrence each > time. > > Cheers, > Warren. > -- > 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]
