Bug 243747 - Comment which is stored in database can't be accessed via digikam
Summary: Comment which is stored in database can't be accessed via digikam
Status: RESOLVED NOT A BUG
Alias: None
Product: digikam
Classification: Applications
Component: Database-Scan (show other bugs)
Version: 1.3.0
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-06 11:33 UTC by Frank Hommes
Modified: 2017-07-26 05:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 1.4.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Hommes 2010-07-06 11:33:57 UTC
Version:           1.3.0 (using KDE 4.4.4) 
OS:                Linux

While looking through my mysql database, i occured to me that many comments which are stored in my mysqldatabase are not shown in digikam!

I checked it this way:
Look up a comment (Table ImageComments), write down the imageid, search for the imageid in table Images, find the photo in digikam. 

I might have to add, the all my photos have a unique filename, which made looking up the photo quite easy. 

Reproducible: Sometimes

Steps to Reproduce:
Of course Digikam never shows the comments but this bug seems to affect only old comments. When I add a new comment, Digikam shows it.
Comment 1 Marcel Wiesweg 2010-07-06 13:32:38 UTC
How where these comments added: Old digikam version? (which?) Read from metadata?

Did you check that the image is digikam is really the one you identified in the database (Images.status=1, Images.album -> Albums.albumRoot -> your current collection)?
Comment 2 Frank Hommes 2010-07-06 13:50:52 UTC
ok, I just found out that I have 75% corrupted entries in my database.
All those images have no Album link (NULL).

So my problem is now, that I got a picture in my database with a comment (the comment is right and fits to the picture) which is not linked to an album.

I got the right picture but without the comment.

I can't tell when this problem started :( I'm using Digikam since 0,9beta10 or something like this and the picture is from 2003.

Maybe I can fix this for my collection but what if more people are affected?
Comment 3 Frank Hommes 2010-07-06 13:58:40 UTC
I guess this problem occurs when you move pictures with the filemanager and the comment has not been saved yet. Something like that.
Comment 4 Marcel Wiesweg 2010-07-06 17:19:10 UTC
Entries with status != 1 and no album are normal, these are deleted images the entries of which are kept for some time (maybe the garbage cleaner is broken).

Normally digikam detects moved files by the hash it stores. Something may have gone wrong, if the comment is not written to the metadata.

Question is: can you reproduce problems now?
Comment 5 Frank Hommes 2010-07-07 09:20:12 UTC
"Normally digikam detects moved files by the hash it stores. Something may have
gone wrong, if the comment is not written to the metadata."

This might have caused my problems... Two years ago, I changed all filenames to a unique system via script and also changed exifdata so digikam wouldn't find those images.

I guess we can close this bug since I can't reproduce the missing comment at the moment. If it should happen again, I will open it again.