Summary: | Comment which is stored in database can't be accessed via digikam | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Frank Hommes <freanki> |
Component: | Database-Scan | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 1.3.0 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.4.0 | |
Sentry Crash Report: |
Description
Frank Hommes
2010-07-06 11:33:57 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)? 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? I guess this problem occurs when you move pictures with the filemanager and the comment has not been saved yet. Something like that. 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? "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. |