[kronolith] Alarms occurs directly after creating a new entry

[Chuck Hagenbuch]

Quoting Mario Liehr <mario at liehr.org>:

> 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.

I'd missed that patch - I agree. It's committed now, and will be in  
RC4 or the final Horde 3.2 release, whichever comes first.

-chuck

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