https://bugs.kde.org/show_bug.cgi?id=522204
Peter <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from Peter <[email protected]> --- (In reply to Maik Qualmann from comment #1) > We set `SET FOREIGN_KEY_CHECKS=0` during the update. Since this does not > appear to be working with your database, you may need to try setting it > globally on a temporary basis. We have not received any other bug reports > regarding this, so it appears to be an isolated issue. > > Just a note: you are using MySQL, whereas we essentially only support > MariaDB now. > > Maik Hi Maik, I struggled with the exact same issue on both Linux and Windows using a MySQL database. I solved it by creating new database tables and using digiKam's database migration feature (...it took a very long time for the migration of the database containing 200,000 photos to complete). It is a truly frustrating bug (bug?). As digiKam consistently uses the term "MySQL" in its Settings, making it unclear that MySQL is actually not supported, only MariaDB. -- You are receiving this mail because: You are watching all bug changes.
