How to work on mobility on a copy of database

[Laurent Hugé-2]

Hi everybody,

Please be gentle for my English...
I've tried and found an solution for my problem, but I'm beginning to
wonder if Digikam is able to work in my way (and that could be my end
with that wonderful tool, sadly)...

At my work, I use to work on Digikam on a powerful computer, enough to
work fast on pictures.
But for professional reasons, I'm obliged to travel a lot, and I want to
work on a copy of the Digikam directory (in case my laptop is stolen, of
course, but also because I use an internal drive at work, which can't be
extracted).
To synchronise the two directories, I use Unison, but I think it doesn't
matter.

But I can't propagate the modifications of my database on my computer at
work : event if the database is copied, it keep displaying the older
flags and notations...
Googling a while, I've understood that the UUID of the drive is recorded
in database, but in my case the UUID doesn't change.

Is there's a way to copy the database from one drive to another so that
Digikam use it correctly ?

Thanks in advance,
--
Laurent Hugé
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Le 09/01/2016 17:40, Laurent Hugé a écrit :

> Is there's a way to copy the database from one drive to another so that
> Digikam use it correctly ?
>

copy the data to the images?

jdd

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Mick Sulley]

I run DigiKam on my desktop and laptop and use Unison to sync between
them.  If I make changes on Desktop and sync then when open DigiKam on
laptop I get a pop up box with a warning that the collection is no
longer available, but it gives me 3 options -

1 - The collection is still available but the id has changed
2 - Mark the collection as removable
3 - Take no action.

The default is option 1 and if I select that then is takes a bit of time
to reload it all but it then works fine.  The problem is that the
database holds not just the directory path to the album but also the
uuid of the disk.  In my case the path is the same on both machines, but
obviously the uuid is different, so I have to reload it all.  It is
possible to write a bit of SQL to fix this, but I have never got around
to doing it.

Hope that helps
Mick

On 01/02/16 19:55, jdd wrote:

> Le 09/01/2016 17:40, Laurent Hugé a écrit :
>
>> Is there's a way to copy the database from one drive to another so that
>> Digikam use it correctly ?
>>
>
> copy the data to the images?
>
> jdd
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users