| 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 (4609 days ago) |
| Due | |
| Updated | 12/17/2012 (4606 days ago) |
| Assigned | |
| Resolved | 12/17/2012 (4606 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Not A Bug
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.
Priority ⇒ 2. Medium
Patch ⇒ No
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ Event notifications do not work for the current day
Type ⇒ Bug
State ⇒ Unconfirmed
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