https://bugs.kde.org/show_bug.cgi?id=447873
Rafael Linux User <rafael.linux.u...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rafael.linux.u...@gmail.com
--- Comment #3 from Rafael Linux User <rafael.linux.u...@gmail.com> ---
(In reply to Maik Qualmann from comment #2)
> Yes, you need at least digiKam-7.4.0 to solve the problem. The version reads
> the MySQL Error Log if the update fails and will start upgrading the
> database to the new MySQL Server version at the next start.
> To understand it, MariaDB has made major changes to the table structure in
> the database. As long as no changes are made to the database, there is no
> problem. In the case of a change to the tables, it will fail. For the system
> MySQL database, a Cron Job is executed which executes the upgrade. In the
> case of the MYSQL database managed by Digikam, this must either be done
> manually (not quite simple) or automatically from digiKam-7.4.0 or newer.
>
> Maik
Ok. I'll try 7.4.0 stable, cause my database is >70k images and I can't risk
there being a bug and having to rescan all the images again (it takes many
hours). I will report back here on how it went.
Thank you
--
You are receiving this mail because:
You are watching all bug changes.
