[Digikam-devel] [digikam] [Bug 338842] Moving DNG images to another album corrupts DNG properties

[Sander van der Heijden]

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

--- Comment #4 from Sander van der Heijden <smvdheijden at gmail.com> ---
Hi Gilles,

Actually, I did not have read metadata from XMP sidecar turned on.
I have now tested the following scenario:
1. Convert a large number (say > 100) CR2 files to DNG
2. Move the DNG images to another album
with two different settings:
1. With both read from and write to XMP sidecars disabled
2. With both read from and write to XMP sidecars enabled

Before each test run, removed the DNG images from the database.
In both cases some of the DNG images (however not the same images) were not
correctly handled.

As I pointed out earlier, I think something goes wrong in the database when
moving the images.
Images that are correctly moved have the following records present:
3913    {null}    DSRC-6681.dng    3    1    2014-09-07T09:37:28    19843902   
c829922663015c6cea8a6465e3910c2b
4101    25    DSRC-6681.dng    1    1    2014-09-07T09:37:28    19843902   
c829922663015c6cea8a6465e3910c2b

Images that are not correct have the following:
3912    {null}    DSRC-6680.dng    3    1    1970-01-01T01:00:00    0    
4100    25    DSRC-6680.dng    1    1    2014-09-07T09:37:26    20216990   
cbd4efc8f06566fb0e8d4b74f241d3b0

This raises a couple of questions:
- Why are there 2 records for 1 image when it's moved? (and why is not just the
album updated?
- Why are modificiationdate and filesize different for the 2 records?
- What do status 1 and 3 mean?

-- 
You are receiving this mail because:
You are the assignee for the bug.