SUMMARY While I migrated from SQLLite to MySQL (external server), the recognition.db file is still used (not migrated) STEPS TO REPRODUCE 1. DigiKam with SQLite 2. Use of face recognition features 3. Migrate to MySQL 4. Restarting PC OBSERVED RESULT recognition.db is still used by digikam EXPECTED RESULT recognition.db should have been migrated to MySQL and Digikam should not use the file anymore SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION
No the recognition DB is no longer used, just like the thumbnail DB. Did you switch to SQLite in digiKam Settings-> Database after migrating? The recognition DB must be created with the maintenance tool and the option to rebuild the training data. Maik
I mean, of course, switched to MySQL in the database settings. Maik
Created attachment 143695 [details] option on windows - database screenshot of the settings
yes, could it be something missing in the windows version? there is no specific database input in the settings/migrate screen
No, nothing is missing in the Windows version. With the settings in your screenshot, the SQLite DB is definitely no longer used. Remember that if you use different databases that these must all be set up, we described on the Requirements tab. Maik
ok, so we have this bug that the file: recognition.db is still used by digiKam (sqlite), or is it expected?
No, the recognition.db is not used if you are using MySQL. How do you come to the conclusion that the file will continue to be used? Maik
Since it is technically not possible in digiKam that a SQLite recognition.db is still used after the switch to MySQL, I close the bug. Maik
just checking on my side, and the last time the file was modified was 2 weeks ago. so I am not sure whether the problem was connected to digikam (and a reboot was somehow required) whether by a different process (AV...) anyway, issue fixed