Tickets :: [#3554] Adding new events fails with DB Error: unknown error

6.0.0-beta1

9/20/25

Summary	Adding new events fails with DB Error: unknown error
Queue	Kronolith
Queue Version	HEAD
Type	Bug
State	Not A Bug
Priority	2. Medium
Owners
Requester	tpenteker (at) bauer-gsr (dot) de
Created	03/02/2006 (7142 days ago)
Due
Updated	03/24/2006 (7120 days ago)
Assigned	03/02/2006 (7142 days ago)
Resolved	03/24/2006 (7120 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

03/24/2006 10:05:41 AM	Jan Schneider	Comment #5 State ⇒ Not A Bug	Reply to this comment
No further feedback.

03/03/2006 09:20:59 PM	Chuck Hagenbuch	Comment #4	Reply to this comment
Right, but what I'm getting at is that the problem you describe does not match the symptoms you describe. First of all, you haven't told us what database server you use - that's probably relevant. Second, try to figure out if events aren't _shown_, or they aren't _created_.

03/03/2006 11:00:31 AM	tpenteker (at) bauer-gsr (dot) de	Comment #3	Reply to this comment
But that error is in a SELECT, not an INSERT. I get your point but there is still this SELECT statement in lib/Driver/sql.php that fails as '-000-01-01 00:00:00' is no valid date in ISO format..

03/02/2006 05:11:56 PM	Chuck Hagenbuch	Comment #2 State ⇒ Feedback	Reply to this comment
But that error is in a SELECT, not an INSERT.

03/02/2006 07:12:43 AM	tpenteker (at) bauer-gsr (dot) de	Comment #1 State ⇒ Unconfirmed Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ Adding new events fails with DB Error: unknown error Queue ⇒ Kronolith New Attachment: horde.log	Reply to this comment
The mistake seems to be the malformed range for the date specified for the SELECT (see attached horde.log): (...) (event_recurenddate >= '-001-11-27 00:00:00' AND event_start <= '2006-01-02 00:00:00' AND (...)