View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005745||SOGo||Backend Calendar||public||2023-04-17 11:52||2023-04-19 14:23|
|Platform||[Client] Microsoft||OS||Windows||OS Version||10, 11|
|Summary||0005745: MySQL4Exception: ExecutionFailed REASON:Data too long for column 'c_description' at row 1|
Found problem happening upon calendar syncing of CalDavSynchronizer and Sogo.
Seems Oulook adds a lot of data (all the replies) to some quick_appointments so then upon writing to sogo_quick_appointment.c_description data is to large.
It would be great if you could perhaps not throw MySQL4Exception (if limit size of received data is to big) but delete excess data that can not fit in "c_description"?
DEBUG from LOG:
Thanks for any help or upgrades...
|Steps To Reproduce|
Happens every time Outlook-CalDavSynchronizer tries to synchronize to sogo.
|Tags||c_description, caldavsynchronizer, MySQL4Exception|
Hi there, this would be strange to replace current exception with a delete. What is the c_description length in your database ?
I can confirm there is huge amount of data in description and probably exceeds MYSQL-TEXT size (65535 bytes).
I have checked if there is CalDavSynchronizer option to limit description size - but for now haven't found one - will contact them also to verify if there is any advanced options for this purpose...
But still would be great to truncate size of description to let's say 65000 bytes if in origin exceedes 65535 - would solve MySQL-Exception.
Thank you very much for your fast response,
If this is a test instance, can you try to change the column type to
@Sebastien Thanks for help (for the second time)...
I really don't know how, but the error is no longer present.
Only thing we changed on our server is change utf8 -> utf8mb4 in another mySQL problem - this ticket:
...don't know if this ticket is related or not - but now it is working, "MySQL4Exception: ExecutionFailed REASON:Data too long for column" is gone...
So thanks again, please mark as resolved and if we get the same problem in future will reopen and try "MEDIUMTEXT".
|2023-04-17 11:52||arisd||New Issue|
|2023-04-17 11:52||arisd||Tag Attached: c_description|
|2023-04-17 11:52||arisd||Tag Attached: caldavsynchronizer|
|2023-04-17 11:52||arisd||Tag Attached: MySQL4Exception|
|2023-04-17 12:32||sebastien||Note Added: 0016830|
|2023-04-17 13:35||arisd||Note Added: 0016832|
|2023-04-17 13:41||sebastien||Note Added: 0016834|
|2023-04-17 13:48||sebastien||Assigned To||=> sebastien|
|2023-04-17 13:48||sebastien||Status||new => feedback|
|2023-04-19 13:43||arisd||Note Added: 0016854|
|2023-04-19 13:43||arisd||Status||feedback => assigned|
|2023-04-19 14:23||sebastien||Status||assigned => resolved|
|2023-04-19 14:23||sebastien||Resolution||open => fixed|