[Digikam-devel] [Bug 186326] New: Problem running a 1:1 copy of albumtree and digikam db

[krienke at uni-koblenz.de]

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

           Summary: Problem running a 1:1 copy of albumtree and digikam db
           Product: digikam
           Version: unspecified
          Platform: SuSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: digikam-devel at kde.org
        ReportedBy: krienke at uni-koblenz.de


Version:           0.10 rc2 (using KDE 4.2.0)
OS:                Linux
Installed from:    SuSE RPMs

For backup purposes I store all my photos on two different hosts with their own
filesystems. I do the syncing via unison, so all photos and digikams database
are always identical. This worked fine for digikam 0.9. 

Since I am using 0.10 I run into trouble. The problem is, that the system I
syncronize to will not show any albums in digikam. digikam in the album sidetab
then only shows an empty list of albums and no photo. In album setup I can see
that the correct album path and name is defined. If i delete the album and
create it new, digikam will scan the whole albumtree and everything is ok.
However for several 1000 photos this takes very long and is not a good
solution.

The album root path (something like /home/account/photos) where database and
all photos are stored is identical on both systems. 

The only difference is of course the UUID of the underlying filesystem or
device. These data (UUID and Albumpath) are used as far as I could see to
identify an album. Is this the source of my problems? Can I change (via
sqlite3) the entry in AlbumRoots table which looks like this:
volumeid:?uuid=cd2d8a35-8828-4b5f-8fd9-7c6443043998
to something different, so digikam will only use the path to the album but not
a uuid of a device?

Any idea?

Thanks
Rainer

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.