Please close this one, it was caused by the invalid permissions to 
add/update/delete events in the kronolith application.

Sorry for the noise.

This doesn't make much sense - why does a SELECT statement cause 
adding an event to fail? Are you sure these two things are related?

When trying to add a new event (Organizing -> Calendar -> New Event), 
it fails because of a bad SQL statement with regarding to the 
event_end statements:



SELECT event_id, event_uid, event_description, event_location, event_s

tatus, event_attendees, event_keywords, event_title, event_category, event_

recurtype, event_recurenddate, event_recurinterval, event_recurdays, event_

start, event_end, event_alarm, event_modified, event_exceptions, event_crea

tor_id FROM kronolith_events WHERE calendar_id = 'edwin' AND ((event_end >

'-001-11-27 00:00:00' AND event_start < '2004-01-02 00:00:00') OR (event_re

curenddate >= '-001-11-27 00:00:00' AND event_start <= '2004-01-02 00:00:00

' AND event_recurtype != 0)).



Invalid input syntax for type timestamp: "-001-11-27 00:00:00"



(this error is shown in the log of the database server, it doesn't 
show up in Kronolith itself)



This is with a PostgreSQL database backend.



If you need more information please let me know.