On 4/29/05, Dave Rolsky <[EMAIL PROTECTED]> wrote: > Has anyone done any work on this?
A little. And I haven't come up with anything more clever then rollout occurrences when requested, and cache them. If someone does come up with something, I'd love to hear about that. I've always felt like there should be a clever algorithm for this, but I haven't found it. We store the start and end dates of the recurrence, and do two queries, one for non-repeating events, and one for repeating events, and repeating event exceptions in the date range. Actually recurrence exceptions are one really good reason why its hard to ever come up with an elegant, purely rule based recurrence representation. For events involving humans its inevitable that sometimes this month's occurrence will get cancelled or re-scheduled. -kellan
