Bug 366092 - Individual database names are always reset to Database Name
Summary: Individual database names are always reset to Database Name
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Setup-Database (show other bugs)
Version: 5.0.0
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-25 15:30 UTC by Simon
Modified: 2021-12-28 17:22 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.5.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon 2016-07-25 15:30:29 UTC
As I want digikam to access the database from ram I configured it to store its database in /tmp. Therefore I changed this line in digikamrc:
    Database Name=/tmp/digikam-db/
    Database Name Face=/tmp/digikam-db/
As the thumbnails database is way too big to be stored in ram I want it to be located on my harddisk:
    Database Name Thumbnails=/media/ntfs_data/Programme/AppDaten/digikam5/thumbnails-digikam.db
When I start digikam (with my old database or completely clean start) these values are automatically set to:
    Database Name=/tmp/digikam-db/
    Database Name Face=/tmp/digikam-db/
    Database Name Thumbnails=/tmp/digikam-db/
Individual storage places are essential for my use case.


Reproducible: Always

Steps to Reproduce:
1. Add different locations "Database Name" and "Database Name Thumbnails" in digikamrc
2. Start digikam

Actual Results:  
"Database Name Thumbnails" is set to the same location as "Database Name" 

Expected Results:  
"Database Name Thumbnails" remains separate from "Database Name" and thus the thumbnail database is located at a different location than the main digikam database.

I used digikam compiled from commit "19446b5" when this happened.
Comment 1 caulier.gilles 2016-07-27 07:44:41 UTC

*** This bug has been marked as a duplicate of bug 297922 ***
Comment 2 caulier.gilles 2021-12-28 17:22:13 UTC
Fixed with bug #297922