https://bugs.kde.org/show_bug.cgi?id=394839
Daniel Vrátil <dvra...@kde.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Latest Commit| |https://commits.kde.org/ako | |nadi/c059d054251282c3bc8d94 | |6447fb156d4442afa3 Status|REPORTED |RESOLVED --- Comment #8 from Daniel Vrátil <dvra...@kde.org> --- Git commit c059d054251282c3bc8d946447fb156d4442afa3 by Daniel Vrátil. Committed on 10/06/2019 at 09:21. Pushed by dvratil into branch 'master'. Raise limit for PimItem.remoteId to 1024 characters Summary: Some DAV servers produce exteremely long RIDs that do not fit into the current 255 character limit. This is only problem on MySQL, on other DBs we use TEXT, which has no length limit. On MySQL, just increasing the column length to 1024 is not enough, there's a limit on maximum length of VARBINARY/VARCHAR index, which is 756 bytes (255 characters). To be able to have an index on a VARBINARY column with up to 1024 characters we need to enable innodb_large_prefix and change how the extra characters are stored on the disk (ROW_FORMAT). Test Plan: Modified a unit-test to attempt creating an Item with 1024 characters long RID Reviewers: #kde_pim, vkrause Reviewed By: #kde_pim, vkrause Subscribers: kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D21714 M +2 -0 autotests/libs/itemappendtest.cpp M +2 -2 src/server/storage/akonadidb.xml M +6 -1 src/server/storage/dbinitializer_p.cpp M +6 -0 src/server/storage/dbupdate.xml M +3 -0 src/server/storage/mysql-global-mobile.conf https://commits.kde.org/akonadi/c059d054251282c3bc8d946447fb156d4442afa3 -- You are receiving this mail because: You are the assignee for the bug.