I'm working through a project utilizing the Kendo UI Scheduler. I am trying to decide how to best handle the RecurrenceExceptions for recurring events. The recurring events work perfectly fine and I think I have my head wrapped around handling sine exceptions, but what about multiples?
For instance, we have a meeting that happens every Tuesday:
RecurrenceRule is "FREQ=WEEKLY;INTERVAL=2;BYDAY=TU"
If someone wanted to cancel this once, the RecurrenceException would look something like this: "20150519T140000Z;"
* from my understanding, the RecurrenceException tells the scheduler not to show the recurring event on this date/time.
What about multiples times? Do I really have to parse an ever-growing delimited by a semicolon? That doesn't seem very practical in the long run. Yes I get it will be awhile before it becomes a problem, but is there a better way to handle this than splitting a long string in the database?
It would seem to me that the better way would be to reference the original recurrence in a new event and then designate the rule there that would pertain to the first one. It makes more sense to me to have multiple entries that are exceptions to the rule rather than track all the exceptions in one field.
What's a practical way around this?