6.0.0-beta1
7/6/25

[#11886] Event notifications do not work for the current day
Summary Event notifications do not work for the current day
Queue Kronolith
Queue Version Git master
Type Bug
State Not A Bug
Priority 2. Medium
Owners jan (at) horde (dot) org
Requester thomas.jarosch (at) intra2net (dot) com
Created 12/14/2012 (4587 days ago)
Due
Updated 12/17/2012 (4584 days ago)
Assigned
Resolved 12/17/2012 (4584 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
12/17/2012 05:04:40 PM Thomas Jarosch Comment #2
State ⇒ Not A Bug
Reply to this comment
Bug in my sqlite 3.6.22 version.

Horde alarm issues this query:

SELECT alarm_id, alarm_uid, alarm_start, alarm_end, alarm_methods, 
alarm_params, alarm_title, alarm_text, alarm_snooze, alarm_internal 
FROM horde_alarms WHERE alarm_dismissed = 0 AND ((alarm_snooze IS NULL 
AND alarm_start <= '2012-12-17T16:26:22') OR alarm_snooze <= 
'2012-12-17T16:26:22') AND (alarm_end IS NULL OR alarm_end >= 
'2012-12-17T16:26:22') AND (alarm_uid IS NULL OR alarm_uid = '' OR 
alarm_uid = 'admin') ORDER BY alarm_start, alarm_end

-> sqlite returns nothing for this.

If I replace the "T" in the datetime in this query with a simple " ", 
sqlite returns the correct result. After returning the correct result, 
even the "T" version starts working.

-> I'll update my sqlite3 version soonish and try again.

12/14/2012 11:25:48 AM Thomas Jarosch Assigned to Jan Schneider
 
12/14/2012 11:25:25 AM Thomas Jarosch Comment #1
Priority ⇒ 2. Medium
Patch ⇒ No
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ Event notifications do not work for the current day
Type ⇒ Bug
State ⇒ Unconfirmed
Reply to this comment
Hi,

I create an event on the current day and configure the custom alarm 
notification
to trigger 15 -days- before the event. So it should trigger immediately.

-> The notification does not trigger.

Moving the event to the next day immediately triggers the notification.
Same behaviour with the SQL and Kolab backend.

Cheers,
Thomas

Saved Queries