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

--- Comment #5 from Stefano Pettini <stefano.pett...@gmail.com> ---
Which commit? If you're talking about this:

> FWIW2: wasn't this fixed already in master by this commit: 
> http://commits.kde.org/amarok/
> 00dd8b41143ce08d1f529b439a943fd9bd052341 ?

this is the commit that introduced the problem. The bug is with the latest
2.8-git and recent versions of MySQL 100% reproducible, and will be fixed when
Terje's patch is merged.

See my comment:

The commit of 2013 linked above tried to fix a problem occurred in the past by
using the deprecated --myisam-recover instead of the proper one
--myisam-recover-options. I assume there was a good reason for this choice, but
now recent MySQL versions don't accept the deprecated option anymore so that
fix should be reverted.

His patch is now on https://git.reviewboard.kde.org/r/128157/

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to