| Summary: | No further updates to and from IMAP account [regression] | ||
|---|---|---|---|
| Product: | [Applications] kmail2 | Reporter: | Rolf Eike Beer <kde> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | Keywords: | regression |
| Priority: | NOR | ||
| Version: | 4.9.95 RC1 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Bug Depends on: | |||
| Bug Blocks: | 295700 | ||
|
Description
Rolf Eike Beer
2013-01-03 16:29:33 UTC
Somehow the "binlog_format=row" that was the fix for bug 289097 got lost from the config file during the upgrade (it wasn't me!). This then leads to error messages like this: Error during executing query "INSERT INTO CollectionTable (remoteId, remoteRevision, name, resourceId, cachePolicyInherit, cachePolicyCheckInterval, cachePolicyCacheTimeout, cachePolicySyncOnDemand, cachePolicyLocalParts) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8)" : "Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED. QMYSQL3: Unable to execute statement" Those can only be observed if starting KMail from a terminal and akonadi not already running. Adding back the binlog_format=row to the config file fixed my problem. |