[digikam] [Bug 267131] SETUP : digiKam config and data cannot be moved, absolute paths embedded in database and digikamrc

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=267131

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
   Version Fixed In||8.1.0
 Resolution|--- |FIXED

--- Comment #28 from caulier.gil...@gmail.com ---
Following Maik comment #2@ and later, i considerate this file as solved now. I
close it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 267131] SETUP : digiKam config and data cannot be moved, absolute paths embedded in database and digikamrc

[Metal450]

https://bugs.kde.org/show_bug.cgi?id=267131

--- Comment #27 from Metal450  ---
Sorry, nevermind, I found it. I thought the "refresh" icon was for refresh
(it's the same icon as when you right-click an album & select "Refresh" - turns
out that on this dialog, the icon means "switch location."

Got it & done, thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 267131] SETUP : digiKam config and data cannot be moved, absolute paths embedded in database and digikamrc

[Metal450]

https://bugs.kde.org/show_bug.cgi?id=267131

--- Comment #26 from Metal450  ---
Apologies - I'm giving 8.0.0 a try, and I can't seem to find the option to move
the existing collection from Local to Network. When adding a new Network
collection from scratch, I do see the new "+" button, "Append a path to the
collection." But I'm not sure how to "switch" my current Local connection to
Network. If I remove Local & re-add the same path as Network, it does start a
full re-scan (I backed up my previous db before trying).  I tried i.e. dragging
that entry from "Local" to "Network" - just a guess - but that doesn't work.
Could you specify where is the UI to switch a Local collection to Network?

Thanks again for all the replies

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 267131] SETUP : digiKam config and data cannot be moved, absolute paths embedded in database and digikamrc

[Maik Qualmann]

https://bugs.kde.org/show_bug.cgi?id=267131

--- Comment #25 from Maik Qualmann  ---
Yes, the solution from Bug 456749 would also work with digiKam-7.x.x.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 267131] SETUP : digiKam config and data cannot be moved, absolute paths embedded in database and digikamrc

[Metal450]

https://bugs.kde.org/show_bug.cgi?id=267131

--- Comment #24 from Metal450  ---
Cool - I didn't see that in v7 stable, perhaps it's a new option in v8.

I just found your other comment here
https://bugs.kde.org/show_bug.cgi?id=456749#c4 - just curious, is the 8.0
feature simply a UI for appending a 2nd mountpoint query arg in the sqlite db?
So I could effectively accomplish the exact same, while still using the v7
stable version? Or does v8 actually have other related fixes, so it's better to
use v8 pre-release, even if it might be less stable?

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 267131] SETUP : digiKam config and data cannot be moved, absolute paths embedded in database and digikamrc

[Maik Qualmann]

https://bugs.kde.org/show_bug.cgi?id=267131

--- Comment #23 from Maik Qualmann  ---
You can switch a local collection to a network collection in the collection
settings without rescanning everything. A network collection can also be a
local partition. The only difference is that with a network collection, the
collection is identified by path and not by a drive UUID.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 267131] SETUP : digiKam config and data cannot be moved, absolute paths embedded in database and digikamrc

[Metal450]

https://bugs.kde.org/show_bug.cgi?id=267131

--- Comment #22 from Metal450  ---
Ah, very cool!

So even if the images are technically stored in a shared partition of the
internal local ssd, I should add it as "Collections on Network Shares"?
(Meaning that if I have an existing Local Collection, I should remove that, &
reestablish the same data as Collections on Network Shares?)

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 267131] SETUP : digiKam config and data cannot be moved, absolute paths embedded in database and digikamrc

[Maik Qualmann]

https://bugs.kde.org/show_bug.cgi?id=267131

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #21 from Maik Qualmann  ---
In digiKam-8.0.0, additional base paths can be "attached" to a network
collection in the collection settings. The respective base path that exists on
the operating system is then used.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 267131] SETUP : digiKam config and data cannot be moved, absolute paths embedded in database and digikamrc

[Metal450]

https://bugs.kde.org/show_bug.cgi?id=267131

--- Comment #20 from Metal450  ---
Edit: another common solution is to specify paths relative to the database
location, i.e. ../../photos, which would also allow for the same.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 267131] SETUP : digiKam config and data cannot be moved, absolute paths embedded in database and digikamrc

[Metal450]

https://bugs.kde.org/show_bug.cgi?id=267131

Metal450  changed:

   What|Removed |Added

 CC||metal...@gmail.com

--- Comment #19 from Metal450  ---
(In reply to Simon from comment #16)
> Yes this is still the same. There is no way to move a collection. The
> location of a collection is stored in the database, so it has to be manually
> adjusted in the database. Currently digikam sees that all files vanished, so
> deletes them in database and the only thing you can do is creating a new
> collection at the new location, obviously losing all information stored in
> the database. A solution within the current framework would be a function
> within digikam to move a collection.
> In my opinion much better would be to take a different approach at storing
> collection locations: Keep them separate from the database either in the
> existing or a new configuration file. That means all the paths in the
> database should be relative to root and the path to root is stored in this
> configuration file. This allows for easily changing the location of a
> collection and even for two digikam instances to share a database (not
> simultaneously, of course, but if that is a worry, that should be solved by
> locking). A use case would be if data and database were shared over a
> network and both could be accessed on different computers.

Has this been addressed yet? In particular, I'm interested in: "all the paths
in the database should be relative to root and the path to root is stored in
this configuration file" - for the purpose of sharing one database on a
WIn+Linux dual boot machine, rather than needing to maintain double databases &
double thumbnails for what is really the same photo collection. For other
software, this is how it has always worked: I specify a base path, and as all
other paths are relative, the same database can be used by both.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 267131] SETUP : digiKam config and data cannot be moved, absolute paths embedded in database and digikamrc

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=267131

--- Comment #18 from caulier.gil...@gmail.com ---
MAik,

No improvements done with last versions cannot help to solve this issue ?

Gilles

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 267131] SETUP : digiKam config and data cannot be moved, absolute paths embedded in database and digikamrc

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=267131

--- Comment #17 from caulier.gil...@gmail.com ---
digiKam 7.0.0 stable release is now published:

https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/

We need a fresh feedback on this file using this version.

Best Regards

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 267131] SETUP : digiKam config and data cannot be moved, absolute paths embedded in database and digikamrc

[Nick Cross]

https://bugs.kde.org/show_bug.cgi?id=267131

Nick Cross  changed:

   What|Removed |Added

 CC||k...@goots.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 267131] SETUP : digiKam config and data cannot be moved, absolute paths embedded in database and digikamrc

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=267131

swatilodh...@gmail.com changed:

   What|Removed |Added

Version|4.6.0   |5.1.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 267131] SETUP : digiKam config and data cannot be moved, absolute paths embedded in database and digikamrc

[Simon via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=267131

Simon  changed:

   What|Removed |Added

 CC||freisi...@gmail.com

--- Comment #16 from Simon  ---
Yes this is still the same. There is no way to move a collection. The location
of a collection is stored in the database, so it has to be manually adjusted in
the database. Currently digikam sees that all files vanished, so deletes them
in database and the only thing you can do is creating a new collection at the
new location, obviously losing all information stored in the database. A
solution within the current framework would be a function within digikam to
move a collection.
In my opinion much better would be to take a different approach at storing
collection locations: Keep them separate from the database either in the
existing or a new configuration file. That means all the paths in the database
should be relative to root and the path to root is stored in this configuration
file. This allows for easily changing the location of a collection and even for
two digikam instances to share a database (not simultaneously, of course, but
if that is a worry, that should be solved by locking). A use case would be if
data and database were shared over a network and both could be accessed on
different computers.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 267131] SETUP : digiKam config and data cannot be moved, absolute paths embedded in database and digikamrc

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=267131

swatilodh...@gmail.com changed:

   What|Removed |Added

 CC||swatilodh...@gmail.com

--- Comment #15 from swatilodh...@gmail.com ---
Is the file still valid using digiKam 5.1.0?
Users are requested to test and provide necessary updates.

-- 
You are receiving this mail because:
You are watching all bug changes.