[digiKam-users] Sharing Digikam albums - what are the issues?

Chris Green cl at isbd.net
Tue Sep 18 16:37:38 BST 2018

Remco Viëtor <remco.vietor at wanadoo.fr> wrote:
> On mardi 18 septembre 2018 16:43:01 CEST Chris Green wrote:
> > I have a large[ish] main 'pictures' album on my desktop machine and
> > use Digikam to manage it.
> > 
> > If I want to duplicate the installation on my laptop what sort of
> > issues might I run into?
> > 
> > The laptop and the desktop both run xubuntu 18.10 and I will
> > (probably) run Digikam 5.9 from an Appimage on both.
> > 
> > As long as I don't run Digikam on both systems at the same time can I
> > synchronise the two (using rsync or whatever) without problems?  Will
> > Digikam's databases (I use sqlite) be OK being synchronised like this?
> One issue that pops up straight away: if you make changes to both the 
> databases (laptop and desktop) between syncs, rsync will keep the newest, it 
> won't do anything to merge changes. So you'd lose all the modifications since 
> last sync in one of the databases. 
Yes, of course, I realise that.

> That will happen with any program that just copies files w/o knowing anything 
> about the contents of those files. Even a utility that understands sqlite 
> databases might not be able to do an unattended merge (in case an item differs, 
> which one to keep? date/time of last file change isn't enough).
I guess this is the *real* problem. If one changes image A on system A
and then iamge B on system B it's (relatively) easy to copy the new
versions from A -> B and B -> A respectively (using --update with
rsync for instance) but with the database you're stuck!  Thanks for
pointing this out.

It thus seems it would make more sense to only copy the image files
and let Digikam update the database, this isn't too difficult.

Chris Green

More information about the Digikam-users mailing list