Bug 519443 - [master Qt6] UpdateSchemaFromV16ToV17 not implemented for QMYSQL / MariaDB
Summary: [master Qt6] UpdateSchemaFromV16ToV17 not implemented for QMYSQL / MariaDB
Status: RESOLVED NOT A BUG
Alias: None
Product: digikam
Classification: Applications
Component: Database-Migration (other bugs)
Version First Reported In: unspecified
Platform: Mint (Ubuntu based) Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-04-26 17:06 UTC by pascal lacroix
Modified: 2026-05-01 19:14 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 9.1.0
Sentry Crash Report:

Attachments
Qmysql log when starting digikam (959 bytes, text/x-log)
2026-04-26 17:06 UTC, pascal lacroix 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description pascal lacroix 2026-04-26 17:06:51 UTC 
Created attachment 191821 [details]
Qmysql log when starting digikam

Version : digiKam master (Qt6 branch, compiled with kde-builder)
Platform : Linux Mint (Debian-based)
Database : External MariaDB (QMYSQL driver), user root on 127.0.0.1:3306

When starting digiKam, the following error appears:

digikam.dbengine: No DB action defined for "UpdateSchemaFromV16ToV17" ! Implementation missing for this database type ( "QMYSQL" ).
digikam.dbengine: Attempt to execute null action
digikam.coredb: Core database: cannot process schema initialization

This prevents any schema upgrade from version 16 to 17 with MySQL/MariaDB.
SQLite works without issue.

Steps to reproduce:
1. Compile latest digiKam master with kde-builder (graphics/digikam, Qt6)
2. Configure digiKam to use external MariaDB database
3. Start digiKam

Expected: Schema update 16→17 should work for QMYSQL like it does for SQLite.
Actual: Migration is blocked because the DB action is missing.

Additional info:
- Build with Qt 6.10 and kde builder
- Database names: all "digikam" (core, thumbs, face, similarity)
- mariadb  Ver 15.1 Distrib 10.11.14-MariaDB, for debian-linux-gnu (x86_64) using  EditLine wrapper
- linux mint 22-3
Comment 1 Maik Qualmann 2026-04-26 17:13:24 UTC 
Everything is present; this is an installation bug on your end. Your installation is accessing an outdated dbconfig.xml file. If you installed digiKam from Git in a different directory, you need to adjust the paths accordingly.

Maik
Comment 2 pascal lacroix 2026-04-26 19:25:43 UTC 
Thanks, corrected, I had an env mistake !

digiKam: 9.1.0
KDE Frameworks: 6.26.0
Qt: Using 6.10.1 and built against 6.10.1
Linux Mint 22.3 (Xcb)
Build ABI: x86_64-little_endian-lp64
Kernel: linux 6.14.0-37-generic
Comment 3 Maik Qualmann 2026-04-26 19:30:06 UTC 
Thanks for the feedback. This update is specifically for MySQL/MariaDB to improve performance with many items.

Maik
Comment 4 Peter 2026-05-01 18:08:14 UTC 
OS: Linux Mint 22.3
App: digiKam 9.1 (digiKam-9.1.0-20260501T140117-Qt6-x86-64.appimage)

The same error ("This prevents any schema upgrade from version 16 to 17") occurs when using the AppImage file as well (source: https://files.kde.org/digikam/).
Comment 5 Peter 2026-05-01 18:12:06 UTC 
(In reply to Peter from comment #4)
> OS: Linux Mint 22.3
> App: digiKam 9.1 (digiKam-9.1.0-20260501T140117-Qt6-x86-64.appimage)
> 
> The same error ("This prevents any schema upgrade from version 16 to 17")
> occurs when using the AppImage file as well (source:
> https://files.kde.org/digikam/).

I could only fix the bug inside digiKam using database migration.
Comment 6 Maik Qualmann 2026-05-01 19:14:58 UTC 
No, I cannot reproduce this in a normal installation; AppImage loads the dbconfig.xml file from the internal AppImage installation in the TEMP directory. This is because we adjust the XDG_DATA_DIRS environment variable accordingly.

Maik