Tickets :: [#925] Value too long importing iCalendar file

6.0.0-beta1

11/4/25

Summary	Value too long importing iCalendar file
Queue	Kronolith
Queue Version	2.0-RC2
Type	Bug
State	Resolved
Priority	2. Medium
Owners	Horde Developers (at)
Requester	srrafa (at) usc (dot) es
Created	12/01/2004 (7643 days ago)
Due
Updated	12/18/2004 (7626 days ago)
Assigned	12/11/2004 (7633 days ago)
Resolved	12/18/2004 (7626 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

12/18/2004 06:16:43 PM	Chuck Hagenbuch	Comment #10 State ⇒ Resolved	Reply to this comment
Okay, there should be more information in the error message now. Resolving.

12/18/2004 09:47:04 AM	Jan Schneider	Comment #9	Reply to this comment
True, I didn't wrap my brain completely around this issue.

12/18/2004 01:34:50 AM	Chuck Hagenbuch	Comment #8	Reply to this comment
Again, how do you want to truncate it though? We don't have that sort of DB error management anywhere.

12/17/2004 06:41:35 PM	Jan Schneider	Comment #7	Reply to this comment
Yeah, the warning is the hard part. But we could still use a truncated title. Do we return the imported event in this code? Then we could display the (now truncated) title of the imported event in the success notification.

12/12/2004 07:09:05 PM	srrafa (at) usc (dot) es	Comment #6	Reply to this comment
By the way, 80 characters is a reasonable size for the event title, but I think making it a little bit longer (let's say 160 chars) does not hurt.

12/12/2004 05:10:07 AM	Chuck Hagenbuch	Comment #5	Reply to this comment
Jan, do you prefer one of these solutions or have another in mind? I think 1 is probably all we can do, we don't have the infrastructure in place to do 2 really...

12/11/2004 03:28:38 PM	Jan Schneider	Assigned to Horde Developers

12/11/2004 03:27:48 PM	Jan Schneider	State ⇒ Assigned

12/11/2004 08:12:29 AM	srrafa (at) usc (dot) es	Comment #4	Reply to this comment
I'd suggest two alternatives: 1. Fail with a more descriptive error message. I was able to track the problem because I have access to the log file., but non-admins will not figure out what's wrong with the calendar. 2. Truncate the offending field and import the calendar issuing a warning that indicates that condition. I think that option 2 is better. I prefer to have my remote calendar imported with some fields truncated than not having it.

12/04/2004 11:31:16 PM	Chuck Hagenbuch	Comment #3 State ⇒ Feedback	Reply to this comment
What do you suggest the alternate behavior should be?

12/01/2004 01:07:58 PM	srrafa (at) usc (dot) es	Comment #2 New Attachment: sts61.ics	Reply to this comment
The file used for the test. Taken from http://ical.mac.com/durban/Nasa32History.ics

12/01/2004 01:07:01 PM	srrafa (at) usc (dot) es	Comment #1 Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ Value too long importing iCalendar file Queue ⇒ Kronolith State ⇒ Unconfirmed	Reply to this comment
When the SUMMARY field of a iCalendar file is too long, the import process fails with DB Error: unknown error This is the error report in the horde log Dec 01 14:05:34 HORDE [error] [kronolith] DB Error: unknown error: INSERT INTO kronolith_events (event_id, event_creator_id, event_title, event_description, event_category, event_location, event_status, event_attendees, event_keywords, event_exceptions, event_modified, event_start, event_end, event_alarm, event_recurtype, event_recurinterval, event_recurenddate, calendar_id)values ('b801edce96a1f108af873670585679f5','srproba','(1985) STS-61-A Challenger Launch - D-1 Spacelab mission (first German-dedicated Spacelab)','',0,'',2,'a:0:{}','','',1101906334,'2003-10-30 00:00:00','2003-10-31 00:00:00',0,5,'1','99991231','52aa0b73abaaf9c217424ead918b012b') [nativecode=ERROR: value too long for type character varying(80)] [on line 359 of "/var/www/horde-3.0-rc2/kronolith-h3-2.0-rc2/lib/Driver/sql.php"]