Bug 219202 - digikam database on multiple hosts
Summary: digikam database on multiple hosts
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Database-Multiusers (show other bugs)
Version: 1.0.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-18 16:33 UTC by rcspam
Modified: 2017-07-26 04:57 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description rcspam 2009-12-18 16:33:57 UTC
Version:            (using KDE 4.3.2)
OS:                Linux
Installed from:    Ubuntu Packages

I have 2 hosts and i use 'unison' to sync the collection directory to see it on both.   Until i upgrade Digikam3 to Digikam4, the digikam3.db database was read bye digikam  very well bye the two hosts. Now after upgrading to the new 1.0 beta then rc version of digikam, the digikam4.db is not read  on the host on which it was not create. Digikam ask me to choose between a local or a removable. The database file can't to be share between the 2 hosts ?? Is it a regression or a bug.  Sorry for my english
Comment 1 Marcel Wiesweg 2009-12-18 18:00:17 UTC
Where are the pictures stored?
Comment 2 rcspam 2009-12-18 19:37:45 UTC
i have the same tree directory on the 2 hosts.
I m not sur what you ask me !! sorry, can you specify please ?
Comment 3 rcspam 2009-12-18 19:42:41 UTC
it s a mirror
Comment 4 rcspam 2009-12-19 09:35:19 UTC
I run digikam on each host and it read pictures and database file on its own HD, i hope this can help you !
Comment 5 Marcel Wiesweg 2009-12-19 15:39:10 UTC
Digikam will see that the two places are different, if you really have stored your images on two different harddisks. If it's stored on a network share, you should add the collection as a "network collection". There is also a solution available to only identify a collection by mount path, by changing the identifier in the database.
Comment 6 rcspam 2009-12-19 18:20:45 UTC
You say: "Digikam will see that the two places are different":
this was not the case with digikam3, i think it is a regression, why not put a relative path in the database or envisage to setting this in preferences with the same behavior as the old version of digikam. It is really handicapping for me, and i m not alone i think, it s not always possible to be near a network. My wife and me can t now look at our 4000 pictures with digikam on our own host. To avoid to wait long minutes that the database to be rebuild completly, i remove digikam4db from the second computer and leave on it the old digikam3.db so the database quickly rebuild partially. But you will acknowledge this is not a solution.
Comment 7 rcspam 2009-12-20 00:02:25 UTC
you say:"There is also a solution available to only identify a collection by mount path, by changing the identifier in the database."
What value for identifier to have the same path on the 2 hosts. Is it possible to name it without any report with the mount path or the volume: can i replace "volumeid:?uuid=4d4762ef-3f13-48cb-805a-0e6168040125" bye for example "My photos" ?
If it is possible, why not put it in the digikam setting interface ?
Comment 8 rcspam 2009-12-20 00:04:57 UTC
PS: Marcel thank you for your patience
Comment 9 Marcel Wiesweg 2009-12-20 15:37:43 UTC
What you need it "volumeid:?mountpath=%2Fyour%2Fmountpath". I'm not absolutely sure but I think the / characters and any non-ASCII char in the path need to be percent-encoded like for any URL.
You should be able to get the same effect if you add the collection as a network collection - these are identified by mount path only currently (until we have found better solutions)
Comment 10 rcspam 2009-12-20 18:26:43 UTC
The problem is that after make change in database and restart digikam, it
reinit the identifier to "volumeid:?uuid=4d47...".
sorry ;(
Comment 11 rcspam 2009-12-20 19:54:56 UTC
It s ok if i put only "volumeid:?mountpath=%2F" in identifier and "the/complet/path/to/the/collection" in specificPath.
Then i arrange symbolic links with the same path on the second host  and it seems ok.
...ouf!
Thank you Marcel and good luke but i really hope this feature to be improve for the 1.0 version
Comment 12 Marcel Wiesweg 2011-03-05 21:34:13 UTC
No changes to be expected, very special case