Bug 481158

Summary: mariadbd as mysql binaries ???
Product: [Applications] digikam Reporter: mahikeulbody <51mfxqck>
Component: Database-AlbumsAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles, metzpinguin
Priority: NOR    
Version First Reported In: 8.3.0   
Target Milestone: ---   
Platform: Manjaro   
OS: Linux   
Latest Commit: Version Fixed/Implemented In: 8.3.0
Sentry Crash Report:
Attachments: with 8.2
with 8.3 appimage bundle

Description mahikeulbody 2024-02-10 10:09:38 UTC
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).
Comment 1 mahikeulbody 2024-02-10 10:10:05 UTC
Created attachment 165719 [details]
with 8.3 appimage bundle
Comment 2 caulier.gilles 2024-02-10 10:24:47 UTC
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
Comment 3 Maik Qualmann 2024-02-10 10:26:38 UTC
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
Comment 4 mahikeulbody 2024-02-10 10:35:10 UTC
Ok, thanks. So why digikam has a migration tool from mysql to mariadb ?
Comment 5 Maik Qualmann 2024-02-10 10:46:53 UTC
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
Comment 6 mahikeulbody 2024-02-10 10:51:44 UTC
Sorry : I confused mysql with sqlite...

(to much kf5 tries is not good for brain care ;-)
Comment 7 Maik Qualmann 2024-02-10 11:13:09 UTC
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
Comment 8 Maik Qualmann 2024-02-10 11:15:02 UTC
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
Comment 9 mahikeulbody 2024-02-10 11:20:03 UTC
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.