[Digikam-devel] [Bug 278927] Not all files read (group items relevant)

[Andreas Mair]

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


Andreas Mair <amair.sob at googlemail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amair.sob at googlemail.com




--- Comment #26 from Andreas Mair <amair sob googlemail com>  2012-01-04 07:25:46 ---
I've also the problem of images that disappeared after playing around with
grouping/versioning. The problem exists in v2.3, v2.4 and v2.5. I've taken a
look at the digikam4.db and found a solution for *my* problem. Maybe it helps
you too.

First you need the sqlite3 tool to open digikam4.db (please work on a backed up
DB!). I use pic.jpg and pic_v1.jpg as my example images.
$ sqlite3 digikam4.db
sqlite> select * from Images where name="pic.jpg" or name="pic_v1.jpg";
322|1|pic.jpg|1|1|2011-09-12T07:42:27|1632259|60c7b5d04416248f228720ed452c13b9
326|1|pic_v1.jpg|1|1|2011-12-22T13:05:31|475912|988fa2584f52daab90221891abf5b109
sqlite> select * from ImageRelations where (subject=322 and object=326) or
(subject=326 and object=322);
322|326|2
326|322|2
sqlite> 

As you can see the images are "linked" in both directions, all working grouped
images are only "one-way linked". Deleting one of that ImageRelations line
brings back the missing images in Digikam.

It's quite easy to get that double linking in Digikam:
- Select two images
- Open the RMB context menu of the *first* image
- Execute "Group / Group selected here"
- If you can't see both pictures now, click the "expand" button to show them
both again.
- If both images aren't selected, select them.
- Open the RMB context menu of the *other* image
- Execute "Group / Group selected here"
- Now both images should have the "versioned" symbol.
- Restart Digikam
- Images are "lost".

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