Bug 468537

Summary: MariaDB error (dbversion)
Product: [Applications] digikam Reporter: Andy <zunar>
Component: Database-MysqlAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: normal CC: caulier.gilles, metzpinguin
Priority: NOR    
Version First Reported In: 7.10.0   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In: 8.1.0
Sentry Crash Report:

Description Andy 2023-04-15 13:46:07 UTC 
Hi!
I want to share my experience.
I had set up a MariaDB on the Synology. But it wasn't possible to work because everything was so very, very slow.
So I installed a SQL server on the PC using Xampp and the database was stored on the Synology.
I've been working a lot with mySQL (MariaDB) the last week. Faces recognized and assigned. I am very surprised that many thousands of faces were incorrectly recognized and assigned. So I ignored many hundreds of faces, assigned different names and so on. It was a lot of work.
Xampp worked fine for a few days. This morning after restarting the PC, the SQL server no longer wanted to run. After I restored the default setting and moved the database from NAS to drive C:, the database ran again. But digiKam didn't want to access it anymore. Something with 'dbversion' and I should create an empty database. The program didn't even start.
I needed to delete the digikamrc file and wanted to migrate the MySQL database to a new SQLite. The connection to MySQL was successful. But data was not migrated. Apparently still no access was possible.
I've given up now. I have now set up digiKam with SQLite and the albums and faces are just being re-recognized. I hope the work of the last few days hasn't been completely in vain.
Regards :-)
Comment 1 Maik Qualmann 2023-04-15 14:04:44 UTC 
When setting up a MySQL database, a lot can go wrong by the user. If the database version cannot be read, there is no "Settings" table. This can have many causes. Without a DebugView log we can't help. Create a DebugView log as described here:

https://www.digikam.org/contribute/

Maik
Comment 2 Andy 2023-04-15 14:34:03 UTC 
Hello and thanks for the answer.
Unfortunately, I can no longer create a debug log. The program is already running again with SQLite. Anyway, I couldn't use MySQL and Xampp as I had hoped. I wanted to run two computers with one database. That does not work. And the SQL server on the Synology was extremely slow.
SQLite runs on drive C:. The folder is synced with Synology Drive. I want to do the same on computer 2 to use the same database. Of course only one computer at a time!
Comment 3 Andy 2023-04-15 18:05:03 UTC 
I wanted to do it again in a VM. I downloaded the DebugViewTool. But I still need to enter user variables somewhere. I do not understand that. My english is limited. I have to run a lot through the translator.

     name: "QT_LOGGING_RULES"
     value: "digikam*=true"
Comment 4 Maik Qualmann 2023-04-15 19:34:46 UTC 
Instead of setting the variables, you can now also activate internal debugging in the digiKam settings under Miscellaneous -> System, then restart digiKam.

Maik
Comment 5 Andy 2023-04-16 11:29:21 UTC 
It took me a while to figure out that you also have to start the DebugView. In the manual there is little information about the switch under 'System'.
But the log helped me a lot and put me on a different path. The database was included in 'phpmyadmin' but I could not open a table. I always got the error 'table doesn't exist in engine'. After my search I found out that suddenly an incorrect 'ibdata1' was included. I restored this file from a backup and the SQL database is working again. I migrated all data from mySQL to SQLite overnight.
:-)
Comment 6 caulier.gilles 2023-05-03 12:39:36 UTC 
Andy,

So this file can be closed now ?

Best regards

Gilles
Comment 7 Andy 2023-05-03 19:00:45 UTC 
Hi Gilles!

Yes!

Regards
Andy