Summary: | information_schema.REFERENTIAL_CONSTRAINTS errors in akonadi server log | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Geert Janssens <info> |
Component: | server | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dvratil |
Priority: | NOR | ||
Version: | 1.10.2 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/akonadi/10d1e2bda3ebc2007f6907b926f02618b2706224 | Version Fixed In: | 1.10.3 |
Sentry Crash Report: |
Description
Geert Janssens
2013-08-24 17:09:32 UTC
REFERENTIAL_CONSTRAINTS column was introduced in MySQL 5.1. This means that on startup Akonadi is not able to verify that all foreign keys are correctly set up in the database, which can cause some troubles when upgrading the database scheme. I recommend you update to at least MySQL 5.1 (or MariaDB) and I will fix Akonadi to check mimimum database version on startup. Git commit 10d1e2bda3ebc2007f6907b926f02618b2706224 by Dan Vrátil. Committed on 26/08/2013 at 12:12. Pushed by dvratil into branch '1.10'. Check minimum MySQL server version Akonadi requires at least MySQL 5.1 (because of using information_schema.REFERENTIAL_CONSTRAINTS column that was introduced in 5.1), so make sure we are running against at least that version. FIXED-IN: 1.10.3 M +30 -0 server/src/storage/dbconfigmysql.cpp http://commits.kde.org/akonadi/10d1e2bda3ebc2007f6907b926f02618b2706224 Thank you for the quick follow up. For now I have reverted to using internal mysql instead of a remote one. In that setup, the errors are gone (Fedora 19 ships mariadb 5.5.31). |