[Tickets #12984] Re: Dismissed Alarms coming back / still poping up on Mozilla Lightning

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/ticket/12984
------------------------------------------------------------------------------
  Ticket           | 12984
  Aktualisiert Von | Jan Schneider <jan at horde.org>
  Zusammenfassung  | Dismissed Alarms coming back / still poping up on
                   | Mozilla Lightning
  Warteschlange    | Kronolith
  Version          | 4.1.4
  Typ              | Bug
  Status           | Feedback
  Priorität        | 2. Medium
  Milestone        |
  Patch            | 1
  Zuständige       | Jan Schneider
------------------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2014-06-16 16:38) hat geschrieben:

>> I'm not sure if it is the best solution to consider all past alarms
>> as dismissed, though it's definitely one solution.
>> Alternatively we could not garbage-collect alarms that have been
>> dismissed, though these alarms will stay in the database forever, or
>> at least until the connected event/task is deleted.
>
> I would vote for the second solution. Let the alarms stay in the db  
> as long as the event is there. If one does not purge the events the  
> additional alarms shouldn't matter, no? But i'm not sure how would  
> this handle never ending recurrent events,  do they pile up in the  
> alarm table "forever"?
>
Any further votes?