[Bug 295700] After upgrade to 4.8.1: QMYSQL3 is unable to execute statement due to BINLOG_FORMAT = STATEMENT

Nico Kruber Nico.Laus.2001 at gmx.de
Mon Mar 12 16:28:43 GMT 2012


https://bugs.kde.org/show_bug.cgi?id=295700

Nico Kruber <Nico.Laus.2001 at gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |Nico.Laus.2001 at gmx.de

--- Comment #2 from Nico Kruber <Nico.Laus.2001 at gmx.de> ---
I'm observing similar problems fetching emails. I can't remember kmail crashing
before this happened, but it won't download new mails anymore
(using KDE packages from either KDE:Distro:Factory or KDE:Release:48 from today
on openSUSE)

Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE ( (
PimItemTable.id = :1 ) )" :  "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" 
Unable to update item access time 
Error during updating record with id 26631  in table "PartTable" "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" 
continuing

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Kdepim-bugs mailing list