[Digikam-users] Syncing Digikam collections and databases between different computers

[Jürgen Blumenschein]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


I have the same problem using the collection on different computers
(e.g. with rsyncing or with nfs-mounts).
Is there a possibility to bring this problem under each users own
responsibility:
An option field in the album/collection dialog to use or not use
uuids. Or if thats not possible to give on (own risk) a fake uuid
via option (e.g. uuid=ffffffff-ffff-ffff-ffff-ffffffffffff).

Jürgen Blumenschein

Am 01.12.2014 um 23:03 schrieb Gilles Caulier:
> UUID is used to identify a disk, especially with removable 
> media.
> 
> Gilles Caulier
> 
> 2014-12-01 21:39 GMT+01:00 Jonathan Ballet <jon at multani.info>:
>> I would be happy to try to propose a patch to remove this from 
>> Digikam, but I would have liked to know first why there was 
>> such an UUID stored (I guess there's a good reason?) and if 
>> there was a chance for a patch to be accepted...
>> 
>> Jonathan
>> 
>> 
>> On Mon, Dec 01, 2014 at 08:25:39PM +0000, Mick Sulley wrote:
>>> Yes agreed!  I think it should be possible to arrange a 
>>> SQLite script to auto run to change the UUID back to what it 
>>> expects, but I have not tried it.  I cannot really see why 
>>> the UUID is in that record at all, the path is there and that
>>> should be sufficient I would have thought.
>>> 
>>> If you do come up with a way to automatically sort it out 
>>> please share.
>>> 
>>> Mick
>>> 
>>> 
>>> On 01/12/14 20:07, Jonathan Ballet wrote:
>>>> Hi Mick,
>>>> 
>>>> thanks for your reply!
>>>> 
>>>> On Sun, Nov 30, 2014 at 06:54:10PM +0000, Mick Sulley 
>>>> wrote:
>>>>> Hi Jonathan,
>>>>> 
>>>>> Yes I raised this when I started using DigiKam, as far as
>>>>> I know there is no proper fix.  If you just accept at the
>>>>> message it works OK, just takes a little time.  It is
>>>>> also possible to add a database script to fix it, here is
>>>>> an answer that I received to that question back in 2013.
>>>>> I never got around to creating the script, I just accept
>>>>> when asked.
>>>> I would be OK just to accept this, but my laptop is not 
>>>> *that* powerful and it takes ages just to rescan all the 
>>>> images, even if nothing changes.
>>>> 
>>>> I'm going to try such a script, as you mentioned, although 
>>>> it's going to be, at best, impracticable.
>>>> 
>>>> I actually wonder what is the purpose of this UUID. If I 
>>>> choose to store the content of Digikam's database into 
>>>> MySQL, is this also stored? I supposed that using a remote 
>>>> database server was to allow sharing between several 
>>>> computers, but if it's stored, that more or less defeats 
>>>> the purpose of having a remote database, isn't it? And if 
>>>> this UUID is not stored, then I wonder what it is using 
>>>> SQLite?
>>>> 
>>>> Hum, I guess I'll need to have a look...
>>>> 
>>>> Jonathan
>> _______________________________________________ Digikam-users 
>> mailing list Digikam-users at kde.org 
>> https://mail.kde.org/mailman/listinfo/digikam-users
> _______________________________________________ Digikam-users 
> mailing list Digikam-users at kde.org 
> https://mail.kde.org/mailman/listinfo/digikam-users
> 


- -- 
Jürgen Blumenschein, eMail: huntington at dokom.net
Homepage: http://huntington-info.eu/
c/o Sozialdienst St. Josef Hospital
Gudrunstraße 56, 44791 Bochum
Tel.: +49 234 509-2428, Fax: +49 234 509-2427
public key:
http://members.dokom.net/blumenschein/Juergen_Blumenschein_(0xC9358EBB)_public_key.asc

- -- 
Jürgen Blumenschein, eMail: blumenschein at dokom.net
Homepage: http://huntington-info.eu/
Am Quartus 17
D-44149 Dortmund
Tel.: +49 231 7217321, Fax: +49 231 47690509
public key:
http://members.dokom.net/blumenschein/Juergen_Blumenschein_(0xC9358EBB)_public_key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)

iEYEARECAAYFAlR9wWIACgkQ7vXR4Mk1jruQkwCg7TDQs6VGlhDrjtg3LfmFXCnU
F10AnjbV8iB3ldmg53Xiy8Yet/RFgFhh
=xG+e
-----END PGP SIGNATURE-----