[Tickets #7689] Re: Clean up recurrence exception edge cases

bugs at horde.org bugs at horde.org
Wed Jan 14 22:30:33 UTC 2009


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7689
------------------------------------------------------------------------------
  Ticket             | 7689
  Updated By         | chorabeblita at belba.com
  Summary            | Clean up recurrence exception edge cases
  Queue              | Kronolith
  Version            | HEAD
  Type               | Bug
  State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Horde Developers
------------------------------------------------------------------------------


Chuck Hagenbuch <chuck at horde.org> (2008-11-14 23:45) wrote:

Right now, exceptions are not copied to a new event when Save As New  
is used. Also, changing the recur_end_date (or the start date) of a  
recurring event does not trim exceptions outside the new range.

I can see situations where trimming exceptions would result in what  
would be considered data loss, but I think the consistent thing to do  
would be:
1. when saving a recurring event, delete recurrence exceptions outside  
the event's range
2. when saving a recurring event As New, copy over recurrences inside  
the new range.

I think 2. is a must; I could be convinced to drop 1.






More information about the bugs mailing list