[kronolith] Alarms occurs directly after creating a new entry

[Mario Liehr]

Chuck Hagenbuch wrote on 17.04.2008 21:26:
> 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?

One have to change the database and the source code for this solution. I 
think the suggestion of Michael Redinger in the comment #10 of the bug 
is the better way. Setting alarm_snooze explicitly makes it independent 
of the default value of this field in the database.

Mario