Re: akonadi fsck fails
Mathias Homann <[email protected]>
| Newsgroups | gmane.comp.kde.users.pim |
|---|---|
| Message-ID | <[email protected]> |
Am Montag, 24. August 2015, 16:39:37 schrieb Daniel Vrátil: > On Friday, August 21, 2015 9:16:51 AM CEST J. Roeleveld wrote: > > Hi all, > > > > Not sure if this is the correct list to post this. > > > > When I run "akonadictl fsck", I notice an error in the > > "akonadiserver.error" logfile showing a SQL-error. > > > > The SQL that is used is over 100,000 characters long, with over 54,000 > > variables that need to be loaded in during the execute-phase. > > > > Is there a way to clean up the "PimItemFlagRelation" table manually to > > ensure this error stops? > > Hi, > > that's a known problem, the query is simply too large and MySQL refuses to > execute it (same with PostgreSQL). I wouldn'd worry too much though - it > does not mean that the database is corrupted or anything. And since we use > database constraints the PimItemFlagRelation table should not contain any > orphaned records (this was added mostly for SQLite). It also does not > affect the rest of fsck process, other checks are executed. > > I should probably look at making the query saner, but that's not the top > priority right now :) Am I the only person who reads this, and thinks "What the *beep* is wrong with whoever developed that? Here we have an END USER application that needs a DATABASE SERVER to work, and the SQL it uses is TOO LARGE for a server-grade sql server???" Just my 2 cents. Cheers MH _______________________________________________ KDE PIM users mailing list Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-users