Bug 322646

Summary: SETUP : SQLITE database for local content, MySQL database for remote
Product: [Applications] digikam Reporter: matteo.fortini
Component: Database-MultiusersAssignee: Digikam Developers <digikam-bugs-null>
Status: REPORTED ---    
Severity: wishlist CC: caulier.gilles, kde.org, kramski
Priority: NOR Flags: kde.org: Junior_Jobs+
Version: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description matteo.fortini 2013-07-21 09:29:11 UTC 
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
Comment 1 kramski 2016-04-07 18:33:04 UTC 
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