Bug 444872 - Create new database
Summary: Create new database
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Setup-CLI (show other bugs)
Version: 7.3.0
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-03 08:43 UTC by Jānis Elmeris
Modified: 2021-11-03 12:09 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jānis Elmeris 2021-11-03 08:43:40 UTC
SUMMARY

There is an option (--database-directory) to open digiKam using a different database, but there is no way of creating a new, different database.

If I want to create a different, independent, unrelated image collection/database and manage it completely independently, I could set up different databases and use --database-directory to choose one upon start-up, but how do I create these different databases?

This is a feature request (unless I'm missing the command to create a new database), so I'm leaving the rest of the fields blank.

STEPS TO REPRODUCE

OBSERVED RESULT

EXPECTED RESULT

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Maik Qualmann 2021-11-03 11:40:42 UTC
Git commit 2c86d69214ed1866dfba576015f27521ca3c4889 by Maik Qualmann.
Committed on 03/11/2021 at 11:39.
Pushed by mqualmann into branch 'master'.

no check for existing SQLite DB with database directory option
FIXED-IN: 7.4.0

M  +1    -1    NEWS
M  +3    -1    core/libs/album/manager/albummanager_database.cpp

https://invent.kde.org/graphics/digikam/commit/2c86d69214ed1866dfba576015f27521ca3c4889
Comment 2 Jānis Elmeris 2021-11-03 11:46:53 UTC
Thank you for the quick reaction!

Can you, please, give a short explanation of what is going to be different now?
Comment 3 Maik Qualmann 2021-11-03 12:09:32 UTC
A dialog was displayed that the database do not exist, this is for normal configuration if the database has been moved by the user. When a database directory option is passed, the database is created automatically.

I would also use the "--config" option, you can then use a separate configuration for each database. Often makes more sense. The config file must exist as an empty file when it is started for the first time.

Maik