<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.kde.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugs.kde.org/"
          
          maintainer="sysadmin@kde.org"
>

    <bug>
          <bug_id>519443</bug_id>
          
          <creation_ts>2026-04-26 17:06:51 +0000</creation_ts>
          <short_desc>[master Qt6] UpdateSchemaFromV16ToV17 not implemented for QMYSQL / MariaDB</short_desc>
          <delta_ts>2026-05-01 19:14:58 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>2</classification_id>
          <classification>Applications</classification>
          <product>digikam</product>
          <component>Database-Migration</component>
          <version>unspecified</version>
          <rep_platform>Mint (Ubuntu based)</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>INVALID</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>NOR</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="pascal lacroix">kikoucalou</reporter>
          <assigned_to name="Digikam Developers">digikam-bugs-null</assigned_to>
          <cc>benedekppeter</cc>
    
    <cc>metzpinguin</cc>
          
          <cf_commitlink></cf_commitlink>
          <cf_versionfixedin>9.1.0</cf_versionfixedin>
          <cf_sentryurl></cf_sentryurl>
          <votes>0</votes>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>2512222</commentid>
    <comment_count>0</comment_count>
      <attachid>191821</attachid>
    <who name="pascal lacroix">kikoucalou</who>
    <bug_when>2026-04-26 17:06:51 +0000</bug_when>
    <thetext>Created attachment 191821
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 &quot;UpdateSchemaFromV16ToV17&quot; ! Implementation missing for this database type ( &quot;QMYSQL&quot; ).
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 &quot;digikam&quot; (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</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2512224</commentid>
    <comment_count>1</comment_count>
    <who name="Maik Qualmann">metzpinguin</who>
    <bug_when>2026-04-26 17:13:24 +0000</bug_when>
    <thetext>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</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2512232</commentid>
    <comment_count>2</comment_count>
    <who name="pascal lacroix">kikoucalou</who>
    <bug_when>2026-04-26 19:25:43 +0000</bug_when>
    <thetext>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</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2512233</commentid>
    <comment_count>3</comment_count>
    <who name="Maik Qualmann">metzpinguin</who>
    <bug_when>2026-04-26 19:30:06 +0000</bug_when>
    <thetext>Thanks for the feedback. This update is specifically for MySQL/MariaDB to improve performance with many items.

Maik</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2513227</commentid>
    <comment_count>4</comment_count>
    <who name="Peter">benedekppeter</who>
    <bug_when>2026-05-01 18:08:14 +0000</bug_when>
    <thetext>OS: Linux Mint 22.3
App: digiKam 9.1 (digiKam-9.1.0-20260501T140117-Qt6-x86-64.appimage)

The same error (&quot;This prevents any schema upgrade from version 16 to 17&quot;) occurs when using the AppImage file as well (source: https://files.kde.org/digikam/).</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2513228</commentid>
    <comment_count>5</comment_count>
    <who name="Peter">benedekppeter</who>
    <bug_when>2026-05-01 18:12:06 +0000</bug_when>
    <thetext>(In reply to Peter from comment #4)
&gt; OS: Linux Mint 22.3
&gt; App: digiKam 9.1 (digiKam-9.1.0-20260501T140117-Qt6-x86-64.appimage)
&gt; 
&gt; The same error (&quot;This prevents any schema upgrade from version 16 to 17&quot;)
&gt; occurs when using the AppImage file as well (source:
&gt; https://files.kde.org/digikam/).

I could only fix the bug inside digiKam using database migration.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2513239</commentid>
    <comment_count>6</comment_count>
    <who name="Maik Qualmann">metzpinguin</who>
    <bug_when>2026-05-01 19:14:58 +0000</bug_when>
    <thetext>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</thetext>
  </long_desc>
      
          <attachment
              isobsolete="0"
              ispatch="0"
              isprivate="0"
          >
            <attachid>191821</attachid>
            <date>2026-04-26 17:06:51 +0000</date>
            <delta_ts>2026-04-26 17:06:51 +0000</delta_ts>
            <desc>Qmysql log when starting digikam</desc>
            <filename>digikam-debug-20260426-185149.log</filename>
            <type>text/x-log</type>
            <size>959</size>
            <attacher name="pascal lacroix">kikoucalou</attacher>
            
              <data encoding="base64">cXQuY29yZS5sb2dnaW5nOiBJZ25vcmluZyBtYWxmb3JtZWQgbG9nZ2luZyBydWxlOiAnZGlnaWth
bS4qPXRydWUgZGlnaWthbS5kYmVuZ2luZT10cnVlIGRpZ2lrYW0uY29yZWRiPXRydWUgZGlnaWth
bS5kYXRhYmFzZT10cnVlIGRpZ2lrYW0uc2NoZW1hPXRydWUgZGlnaWthbS5kYm1hbmFnZXI9dHJ1
ZSBkaWdpa2FtLmNvcmU9dHJ1ZSBxdC5zcWw9dHJ1ZSBxdC5kYj10cnVlICouc3FsPXRydWUnCnF0
Lmd1aS5pY2M6IGZyb21JY2NQcm9maWxlOiBmYWlsZWQgc2l6ZSBzYW5pdHkgMgpxdC5xcGEuc2Vy
dmljZXM6IEZhaWxlZCB0byByZWdpc3RlciB3aXRoIGhvc3QgcG9ydGFsIFFEQnVzRXJyb3IoIm9y
Zy5mcmVlZGVza3RvcC5wb3J0YWwuRXJyb3IuRmFpbGVkIiwgIkNvdWxkIG5vdCByZWdpc3RlciBh
cHAgSUQ6IENvbm5lY3Rpb24gYWxyZWFkeSBhc3NvY2lhdGVkIHdpdGggYW4gYXBwbGljYXRpb24g
SUQiKQpkaWdpa2FtLmRiZW5naW5lOiBObyBEQiBhY3Rpb24gZGVmaW5lZCBmb3IgIlVwZGF0ZVNj
aGVtYUZyb21WMTZUb1YxNyIgISBJbXBsZW1lbnRhdGlvbiBtaXNzaW5nIGZvciB0aGlzIGRhdGFi
YXNlIHR5cGUgKCAiUU1ZU1FMIiApLgpkaWdpa2FtLmRiZW5naW5lOiBBdHRlbXB0IHRvIGV4ZWN1
dGUgbnVsbCBhY3Rpb24KZGlnaWthbS5jb3JlZGI6IENvcmUgZGF0YWJhc2U6IGNhbm5vdCBwcm9j
ZXNzIHNjaGVtYSBpbml0aWFsaXphdGlvbgpkaWdpa2FtLmRiZW5naW5lOiBObyBEQiBhY3Rpb24g
ZGVmaW5lZCBmb3IgIlVwZGF0ZVNjaGVtYUZyb21WMTZUb1YxNyIgISBJbXBsZW1lbnRhdGlvbiBt
aXNzaW5nIGZvciB0aGlzIGRhdGFiYXNlIHR5cGUgKCAiUU1ZU1FMIiApLgpkaWdpa2FtLmRiZW5n
aW5lOiBBdHRlbXB0IHRvIGV4ZWN1dGUgbnVsbCBhY3Rpb24KZGlnaWthbS5jb3JlZGI6IENvcmUg
ZGF0YWJhc2U6IGNhbm5vdCBwcm9jZXNzIHNjaGVtYSBpbml0aWFsaXphdGlvbgo=
</data>

          </attachment>
      

    </bug>

</bugzilla>