https://bugs.kde.org/show_bug.cgi?id=220903 Summary: Duplicate records in ImageComments table after
migration from didkam3.db
Product: digikam
Version: unspecified
Platform: openSUSE RPMs
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo:
[hidden email]
ReportedBy:
[hidden email]
Version: 0.10.0-6.23 (using KDE 4.3.1)
OS: Linux
Installed from: openSUSE RPMs
I have about 22000 images managed in the former digikam3.db under OpenSuse 11.1
that contain a lot of image comments. I did set the option to store the image
comments to the database as well as to the image exif data.
Then with the OpenSuse 11.2 I did migrate the digikam3.db to digikam4.db when I
was using digikam the first time there. Now, some weeks later and another lots
of data changes later - especially on the comments and geolocations - I found
that it seems, I could not update image comments that are originally written in
the digikam3.db.
After recovering from this shock, I did investigate what's really stored in the
digikam4.db and in the image data. Looking at the images with GwenView did show
that all changed comments are stored in the image data. Then, looking at the
database, the SQLite manager of Firefox did show duplicates in the
ImageComments table for all images that had comments written under digikam3.db.
And obviously there are updates made in one of the duplicate records, but not
the one that is read to reflect the changes in the GUI of the comment control.
To be more precise, the duplicates means the records refer to the same image,
but have a unique record id
In other words, making a change on a comment written under digikam3.db does
show:
(1) former comment "My comment"
(2) change it now to "My comment new"
(3) after storing it shows again "My comment", but the new comment is stored in
the image data and in one of the duplicate records.
For me now there is the question, how to get rid of these duplicates. I have
more of 6000 of them, deleting them manually is just not fun.
Another issue is, as these duplicates refer to the same image, but have a
unique record id - so, which record can I delete, what happens after deletion,
system crashes, more inconsistent data?
Are there any suggestions to by-pass the problem or, more welcome, to repair
the database by program?
--
Configure bugmail:
https://bugs.kde.org/userprefs.cgi?tab=email------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Locked
