DT should provide an easy way to backup user library.db
At least every week, Adobe Lightroom prompts the user whether they want to backup
their image catalogue. Darktable should do the same; this would tie in nicely with
providing support for multiple different collection libraries.
#1 Updated by Simon Spannagel about 7 years ago
Hi McBofh! :)
not sure we want this. We only have the db due to performance reasons. afaik everything should be redundant that is in the user's library.db (the processing and metadata for sure, with xmp files, but even styles and presets should be saved as plain text files as well)
I'm not entirely sure about presets but there was the idea to write them to file, too.
I think I wouldn't like dt bothering me with promoting backups. If I want them I just set up a backup procedure outside dt to backup the library.db and other files I want.
What do you think? Would this really be of much use?
#2 Updated by James C. McPherson about 7 years ago
Lightroom doesn't prompt you to promote a backup, it just asks whether you want to make one.
It's always the user's prerogative to do what they want in terms of backups. However, as a user-friendliness item (particularly if people are comparing DT to LR) then having an option to enable automatic backups would be good.
It's simple enough to do with the SQLite Backup API so we don't run into file locking issues at the OS level (copying an open sqlite db from the shell might well leave you with a locked db). My plan is that we'd have
 Enable library.db backups
[daily | weekly] frequency of automatic backup
 prompt me to backup
where the second two options are greyed out unless the first is checked. No customisation of filenames to be allowed, we'd use the format
which is what we'd get from /usr/bin/date +%Y%m%d_%H%M
Re redundancy - yes, we've got everything (or should have) stored on-disk in xmp as well. However, when your library gets large it's a pain to go and reimport everything.