[Tickets #6183] Re: Kronolith gives premature notifications

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/6183
-----------------------------------------------------------------------
 Ticket             | 6183
 Updated By         | Michael.Redinger at uibk.ac.at
 Summary            | Kronolith gives premature notifications
 Queue              | Kronolith
 Version            | 2.2-RC2
 Type               | Bug
 State              | Feedback
 Priority           | 2. Medium
 Milestone          | 
 Patch              | 
 Owners             | Jan Schneider
-----------------------------------------------------------------------


Michael.Redinger at uibk.ac.at (2008-03-22 17:20) wrote:

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