6.0.0-beta1
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
9/11/25
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#6183] Kronolith gives premature notifications
*
Your Email Address
*
Spam protection
Enter the letters below:
.. .. ,. . . ||\/| \./ | | | \__|| | | |__|\__|
Comment
> You are right - that seems to be some problem with the database. > > A closer look at the database showed that all datetime columns where > set to a '1970' default: > > > > `alarm_start` datetime NOT NULL default '1970-01-01 00:00:00', > > `alarm_end` datetime default '1970-01-01 00:00:00', > > `alarm_snooze` datetime default '1970-01-01 00:00:00', > > > > I have not the slightest idea how that happened. I started with > horde-webmail-1.1-rc2 with a clean OS+DB install and only updated the > files to the latest horde/imp RCs since then (and did not touch the > database - that is something I always try to avoid because I am not > well schooled in it ...) > > > > I now dropped the table an recreated it. No more stupid defaults ... > > > > Anyway - I would be nice to know if this solves Eric's problem, too > (I suppose it does). > > > > Thanks, > > Michael
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers