| Summary | Importing event with category name > 80 char fails |
| Queue | Kronolith |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | Jan Schneider <jan (at) horde (dot) org> |
| Requester | patrick (dot) abiven (at) apitech (dot) fr |
| Created | 04/04/2007 (403 days ago) |
| Due | |
| Updated | 04/02/2008 (39 days ago) |
| Assigned | 03/14/2008 (58 days ago) |
| Resolved | 04/02/2008 (39 days ago) |
| Attachments | |
| Milestone | |
| Patch |
State ⇒ Resolved
Assigned to Jan Schneider
Alright, we cut them off at 80 chars now.I would guess single digits.I'm a bit hesitating to hardcode the limit inside the SQL code. It would of course be possible to cut off the categories at 80 chars. OTOH, how many people really do change the default SQL scheme that we provide with Kronolith?PostGreSQL
> Which database do you use? MySQL seems to truncate the category
> automatically.
State ⇒ Feedback
Taken from Karsten Fourmont
Which database do you use? MySQL seems to truncate the category automatically.State ⇒ Assigned
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Summary ⇒ Importing event with category name > 80 char fails
Queue ⇒ SyncML
Hello
In the kronolith_events table, the field event_category is defined as VARCHAR(80). But in kronolith/lib/Driver.php, the setCategory() function doesn't check the size of $category. So importing or synchronizing events having a category name greater than 80 char fails (DB Error: unknown error).
A workaround is to reduce the $category to 80 char.
Regards
Patrick