[kronolith] reccuring events: exceptions?

[Chuck Hagenbuch]

Quoting Jesse Wolff <jesse_wolff@yahoo.com>:

> Exceptions could be actual inserts to the db that are checked against when
> the nextRecurrance is being calculated? It might be feasible because these
> records could just be included in the current SQL select therefore not added 
> extra calls to the db. I'm not familiar with mcal so of course this only 
> applies to the sql driver.

*tweeet!* Backend-specific code, 15 yard penalty and loss of down.

(sue me, I'm punchy)

In all seriousness, it'd be great to see this done, but forget about SQL when
you're mapping it out. It _has_ to fit cleanly into the driver API, and it has
to _not_ rely on side effects of the SQL implementation to work.

> This leads to another question. When a recurring event is viewed or edited 
> should the original event dates and times be displayed (as it is currently)
> or should the specific instance date and times be displayed along with an 
> indication that it's a recurring event. I think I'd prefer the later.

For editing, that would break things badly. Right now there's no difference
between editing and viewing; if that changed, we could talk about it. I'm all
for adding a recurrence icon to the edit screen, though.

-chuck

--
Charles Hagenbuch, <chuck@horde.org>
"What was and what may be lie, like children whose faces we cannot see, in 
the arms of silence. All we ever have is here, now." - Ursula K. Le Guin