Bug 267553

Summary: SETUP : Starting digikam with "--database-directory" prompts for new database folder after any configuration change
Product: [Applications] digikam Reporter: Phil Linttell <phil.linttell>
Component: Setup-DatabaseAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: alpinekid, caulier.gilles, development, swatilodha27
Priority: NOR    
Version: 2.5.0   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In: 7.1.0
Sentry Crash Report:

Description Phil Linttell 2011-03-03 14:45:09 UTC 
Version:           2.0.0 (using KDE 4.6.0) 
OS:                Linux

When starting digikam with an alternative database specified on the command line (via --database-directory), making any change to the digikam configuration will result in a prompt to "Create New" or "Copy Current" database to the default database location.

This is *likely* to result in wiping out an existing, valid, database at that location if digikam has been used before to manage photos without specifying the database directory. 

Exact text of message pop-up:

New database folder - digikam 
You have chosen the folder "/home/phil/.digikam" as the new place to store the database.
Would you like to copy the current database to this location and continue using it, or start with a new database?
[Create New Database] [Copy Current Database]



Reproducible: Always

Steps to Reproduce:
1. Start digikam with alternative database:
digikam --database-directory /tmp/photos
2. Select "Configure Digikam"
3. Change any setting
4. Click ok




Actual Results:  
Exact text of message pop-up:

New database folder - digikam 
You have chosen the folder "/home/phil/.digikam" as the new place to store the database.
Would you like to copy the current database to this location and continue using it, or start with a new database?
[Copy Current Database] [Use Existing File]


(If you go on to "Copy Current Database" your existing, default database is backed up, and a new database created in it's place.)


Expected Results:  
No prompt should appear.  I've specified the database location on the command line and have no wish to move it anywhere else.  

While the existing database is backed up, the user may not realize this.  From their perspective, next time they start digikam (without specifying the database location) their database has been over-written.

While not an actual lose of data, it may lead to the user having a heart-attack.
Comment 1 caulier.gilles 2011-12-15 09:14:42 UTC 
Phil,

This file still valid using digiKam 2.4 ?

Gilles Caulier
Comment 2 Al 2012-12-20 15:42:04 UTC 
I'm using version 2.5.0 with ubuntu 12.4 and gnome and it is stilling happening.

It also doesnt seem to read the database correctly, When I enter the dir name at the command line option --data-directory i dont see the same metadata as when I open digikam from an icon without any parm and then use the configure menu to set the database path.
I'm storing the metadata in xmp sidecar files.

Very scarry the first time this happened.
Comment 3 caulier.gilles 2014-08-07 12:22:34 UTC 
This file still valid with last digiKam 4.2.0 ?

Gilles Caulier
Comment 4 swatilodha27 2016-08-08 14:00:55 UTC 
Is the file still valid using digiKam 5.1.0?
Please test and provide necessary updates.
Comment 5 Glenn Washburn 2017-03-13 22:12:41 UTC 
This is effectively a duplicate of bug 218297.  And yes, it is still a bug in DK 5.4.0.
Comment 6 caulier.gilles 2017-03-18 13:09:01 UTC 

*** This bug has been marked as a duplicate of bug 218297 ***
Comment 7 caulier.gilles 2020-07-26 08:17:39 UTC 
Fixed with #218297