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

2017-01-07 Thread Denis Kurz
https://bugs.kde.org/show_bug.cgi?id=295700 Denis Kurz changed: What|Removed |Added Resolution|WAITINGFORINFO |UNMAINTAINED

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

2016-09-24 Thread Denis Kurz via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=295700 Denis Kurz changed: What|Removed |Added Resolution|--- |WAITINGFORINFO

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

2013-01-23 Thread Christian Mollekopf
https://bugs.kde.org/show_bug.cgi?id=295700 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC|

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

2013-01-23 Thread Christian Mollekopf
https://bugs.kde.org/show_bug.cgi?id=295700 --- Comment #9 from Christian Mollekopf mollek...@kolabsys.com --- Apparently this is still an issue for people from time to time, and documented workarounds start to emerge, so I think we should either figure out what's going on or enforce from akonadi

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

2012-04-18 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=295700 --- Comment #8 from Volker Krause vkra...@kde.org --- My fix indeed was too aggressive for older MySQL versions and has just been reverted. If you are affected by the original problem, please post your ~/.local/share/akonadi/mysql.conf file, or at

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

2012-04-16 Thread Raphael Kubo da Costa
https://bugs.kde.org/show_bug.cgi?id=295700 Raphael Kubo da Costa rak...@freebsd.org changed: What|Removed |Added CC||rak...@freebsd.org

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

2012-04-15 Thread Jonathan Marten
https://bugs.kde.org/show_bug.cgi?id=295700 Jonathan Marten j...@keelhaul.me.uk changed: What|Removed |Added Status|RESOLVED|REOPENED

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

2012-04-14 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=295700 Volker Krause vkra...@kde.org changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO CC|

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

2012-04-14 Thread Volker Krause
https://bugs.kde.org/show_bug.cgi?id=295700 Volker Krause vkra...@kde.org changed: What|Removed |Added Status|NEEDSINFO |RESOLVED

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

2012-04-14 Thread Franz Häuslschmid
https://bugs.kde.org/show_bug.cgi?id=295700 --- Comment #5 from Franz Häuslschmid luk...@gmx.at --- (In reply to comment #3) What MySQL server version are you using? MySQL tells me: ~ /usr/sbin/mysqld --version /usr/sbin/mysqld Ver 5.5.16 for Linux on x86_64 (Source distribution) -- You are

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

2012-03-12 Thread Nico Kruber
https://bugs.kde.org/show_bug.cgi?id=295700 Nico Kruber nico.laus.2...@gmx.de changed: What|Removed |Added CC||nico.laus.2...@gmx.de ---

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

2012-03-10 Thread Franz Häuslschmid
https://bugs.kde.org/show_bug.cgi?id=295700 Franz Häuslschmid luk...@gmx.at changed: What|Removed |Added Summary|After upgrade to 4.8.1: |After upgrade to 4.8.1:

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

2012-03-10 Thread Franz Häuslschmid
https://bugs.kde.org/show_bug.cgi?id=295700 --- Comment #1 from Franz Häuslschmid luk...@gmx.at --- After having updated to 4.8.1 I added an IMAP resource for a dovecot2 mail server. After that process I was trying to load messages (read and unread) from that server. I assume I was hit by the bug