[Digikam-devel] [Bug 222774] many (but not all) tags have been lost after multiple albums facility added

[Jonathan Marten]

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





--- Comment #9 from Jonathan Marten <jjm keelhaul me uk>  2010-01-24 17:28:54 ---
There were indeed two collections defined in digikam settings (but it wasn't
obvious at first glance, because the second was simply labelled "Col0".  Not
sure where this name came from.

Have now changed the settings for a single local collection rooted at
/share/photos (I'm assuming that this is the correct one to use for an
automounter path).  However, after a collection rescan the same tags are still
missing.

I've done a bit of looking round in the database (with sqlitebrowser) for one
of the images that has lost its tags.  These are what hopefully are the
relevant parts of the tables:

Table "Images", rows with "name" = the problem image name:

row      id       album   status   uniqueHash
6        6                3        b7b8a975...
36168    36462            3        b7b8a975...
66449    66743            3        47473fec...
97020    97314            3        47473fec...
127756   128050           3        47473fec...
158502   158796           3        47473fec...
189242   189536   95      1        47473fec...

Table "ImageTags", rows with "imageid" = "id" as above:

row      imageid    tagid
2466     6          1
2467     6          3
2468     6          71
25033    36462      1
25034    36462      3
25035    36462      71

These match the tags as would have been originally set.  There are no entries
in this table matching any of the other "id"s.

The current uniqueHash for the image in question (as calculated in 
DImgLoader::uniqueHash) is indeed 47473fec...

Could the uniqueHash calculation for the image have changed between the time
that it was tagged and now?  The file modtime on disc has not changed, and is
the same as for unaffected images in the same directory.

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