Created attachment 165718 [details] with 8.2 SUMMARY Digikam 8.2 uses mysql binaries to manage my database (see attached screenshot_8.2). Digikam 8.3 (appimage) seems to use mariadb binaries to manage my database (see attached screenshot_8.3).
Created attachment 165719 [details] with 8.3 appimage bundle
The AppImage bundle 8.3.0 pre-release is now compiled under Ubuntu 20.06 instead 18.04. See bug 480134. Probably this Ubuntu version change the mysql install to mariadb on the system. Gilles Caulier
This is not a bug. For the internal database we only support MariaDB. The MySQL binary programs under MariaDB were only symbolic links to the MariaDB binaries. The use of these MySQL symbolic links has already been given deprecated warnings by MariaDB. Maik
Ok, thanks. So why digikam has a migration tool from mysql to mariadb ?
What do you want to migrate? You've always used MariaDB. MySQL could no longer be used for the internal database for a long time because the "mysql_install_db" no longer exists in the original Oracle MySQL. Maik
Sorry : I confused mysql with sqlite... (to much kf5 tries is not good for brain care ;-)
Git commit f3101f7eaf072a0bc27baa57a184f82da0da8eff by Maik Qualmann. Committed on 10/02/2024 at 11:12. Pushed by mqualmann into branch 'master'. use a hidden config option to continue supporting MySQL for a while FIXED-IN: 8.3.0 M +1 -1 NEWS M +37 -4 core/libs/database/engine/dbengineparameters.cpp https://invent.kde.org/graphics/digikam/-/commit/f3101f7eaf072a0bc27baa57a184f82da0da8eff
But you're right, at least with a hidden config option we can still give users who use an Oracle MySQL internal database the opportunity to continue using it. Maik
Ok. My concern was the difference between 8.2 displaying mysql binaries when 8.3 displays mariadb binaries for the same database. I understand now it is a cosmetic difference.