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.