I chose digiKam for managing my quite large collection of photos. The photos reside partly on my NAS, partly on my laptop HDD (when I first download them, when I take them around). Since I have more than one users accessing the photos, using only a local sqlite db is ruled out. Mysql would be the answer, but digiKam would refuse to start unless it can contact mysql. I wish digiKam would handle local/remote content differently, keeping info on local content in sqlite, so it can work offline, and info on remote content in mysql Reproducible: Always Steps to Reproduce: 1. keep collection partly local, partly remote 2. disconnect from the network 3. try to use digikam Actual Results: digikam gives error and can't use local collections Expected Results: use sqlite for local collections
Even with the MySQL backend normally configured, you can run a second Digikam 5.0 setup with the switch "--database-directory <dir>" (Start digikam with the SQLite database file found in the directory <dir>). (Don't know if Digikam 4.x already has this switch.) Heinz