Bug 426791

SUMMARY
After moving my database to a different location on disk, updating the path to the new database in "Configure DigiKam"->"Database" does not seem to actually update the path. Upon restarting digikam, the path still points to the old database location. Only after manually editing digikamrc, did the path show correctly. This is with the MySQL internal database option. I am inclined to think that this probably isn't platform specific.

STEPS TO REPRODUCE
1. Copy an existing mariadb database to a new location disk
2. "Configure Digikam" -> "Database" and update the path to point to the new path.
3. Restart digikam.

OBSERVED RESULT
On my machine, when digikam restarted, all the albums disappeared. "Configure Digikam" -> "Databases" shows the old path.
To confirm my hunch that perhaps the digikamrc file isn't be updated, I opened it and left it open in my editor while I updated the path in digikam and closed the application. No updates to digikamrc were made (as reported by my editor). Upon updating the path in digikamrc, restarting digikam shows all my old albums, and the path in "Configure Digikam" -> "Database" now reflects the new path.


EXPECTED RESULT
I expect the updates to the path in the GUI to "stick" (ie, update digikamrc). I shouldn't have to manually edit digikamrc to change the database location.


SOFTWARE/OS VERSIONS
Windows: 10
(available in About System)
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0