https://bugs.kde.org/show_bug.cgi?id=412777
Bug ID: 412777
Summary: DigiKam+MySQL: Failed to create database tables.
Product: digikam
Version: 6.3.0
Platform: Appimage
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Database-Mysql
Assignee: digikam-bugs-n...@kde.org
Reporter: alexan...@steinhoefer.net
Target Milestone: ---
Created attachment 123107
--> https://bugs.kde.org/attachment.cgi?id=123107&action=edit
stdout-Output from digiKam AppImage
SUMMARY
I have a Synology NAS with a MariaDB-Server running MariaDB:latest (currently
10.4.8-MariaDB-1:10.4.8+maria~bionic) from DockerHub
(https://hub.docker.com/_/mariadb/) on it.. I have full access from the
network. I am using openSUSE Leap 15.1 and tried it with digiKam 6.3.0
(AppImage) as well as 6.0 (from openSUSE's own Leap repositories).
What I do is a fresh install of digiKam, fresh user settings (removed
~/.config/digikamrc/) then start digiKam and fill out the first-run wizard: Add
my NAS photos-folder (smb mount via /etc/fstab) and enter the database settings
for my MariaDB-Server.
I created the user and database as is suggested by the First-Run-Wizard of
digiKam. Database connection check returns an "OK".
After finishing the wizard, digiKam starts creating tables and then after a few
seconds fails with a "table error".
STEPS TO REPRODUCE
1. Start a fresh digikam installation
2. Point Digikam to a directory containing photos
3. Set MySQL as database
4. Enter credentials.
5. Finish Wizard.
OBSERVED RESULT
DigiKam displays an error message and does not correctly initialize the
database.
EXPECTED RESULT
MySQL tables get properly initialized and I can start using digiKam.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Leap 15.1
KDE Plasma Version: 5.12.8
KDE Frameworks Version: 5.55.0
Qt Version: 5.9.7
ADDITIONAL INFORMATION
1. max_allowed_packet is configured to 256M.
2. I've attached the stdout-Output from the 6.0.3-AppImage-Version. tail -10
yields:
Digikam::DbEngineConfigSettingsLoader::readConfig: Loading SQL code from config
file "/tmp/.mount_digikaJpjI5X/usr/share/digikam/database/dbconfig.xml"
Digikam::DbEngineConfigSettingsLoader::readConfig: Checking XML version ID =>
expected: 3 found: 3
Digikam::CoreDbSchemaUpdater::update: Core database: running schema update
Digikam::CoreDbSchemaUpdater::startUpdates: Core database: no database file
available
Digikam::BdEngineBackendPrivate::debugOutputFailedQuery: Failure executing
query:
""
Error messages: "QMYSQL: Unable to execute query" "Cannot load from mysql.proc.
The table is probably corrupted" "1728" 2
Bound values: ()
Digikam::BdEngineBackend::execDBAction: Error while executing DBAction [
"CreateIndices" ] Statement [ "\n DROP PROCEDURE IF EXISTS
create_index_if_not_exists;\n " ]
Digikam::CoreDbAccess::checkReadyForUse: Core database: cannot process schema
initialization
------
3. digiKam apparently managed to create the following tables without errors:
MariaDB [digikam]> show tables;
+--------------------+
| Tables_in_digikam |
+--------------------+
| AlbumRoots |
| Albums |
| DownloadHistory |
| ImageComments |
| ImageCopyright |
| ImageHistory |
| ImageInformation |
| ImageMetadata |
| ImagePositions |
| ImageProperties |
| ImageRelations |
| ImageTagProperties |
| ImageTags |
| Images |
| Searches |
| Settings |
| TagProperties |
| Tags |
| TagsTree |
| VideoMetadata |
+--------------------+
20 rows in set (0,00 sec)
--
You are receiving this mail because:
You are watching all bug changes.
