[kronolith] Alarms occurs directly after creating a new entry

[Chuck Hagenbuch]

Quoting Mario Liehr <mario at liehr.org>:

> Indeed, this bug contains the solution. Actually I searched in the  
> bugs, but I missed this one. Anyway the solution is to remove in the  
> table horde_alarms the default from the entry alarm_snoozed.
>
> As Jan mentioned in the bug, this default seems to be created through
> MDB2. I played a while with the setup script, but found no solution to
> prevent this. Maybe it is a good idea to make somewhere (e.g. after
> creating the databases with setup.php) a statement about this problem or
> add a dirty hack to change the table.

Can we make the default '0000-00-00 00:00:00', make the field not  
null, and check against that zero value instead of null?

-chuck

-- 
"I have concerns that we are not behaving like a mature, responsible,  
collection of interdependent organisms." - Rick O.