[digikam] [Bug 374591] New: Deleting image only removes the file and sets the status to hidden but does not delete the image from DB

Mario Frank bugzilla_noreply at kde.org
Thu Jan 5 12:52:46 GMT 2017


            Bug ID: 374591
           Summary: Deleting image only removes the file and sets the
                    status to hidden but does not delete the image from DB
           Product: digikam
           Version: 5.4.0
          Platform: Compiled Sources
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Database
          Assignee: digikam-devel at kde.org
          Reporter: mario.frank at uni-potsdam.de
  Target Milestone: ---

While doing some tests for bug ids https://bugs.kde.org/show_bug.cgi?id=320666
and https://bugs.kde.org/show_bug.cgi?id=374191 , I moved some image to trash
to make sure that the similarities to this image are deleted. 
While the similarities to this image were deleted, the similarities of the
image to other images were not deleted.

Moving to trash thus obviously does not delete the image properties for the
image moved to trash.

Then, I deleted the image from trash but the image properties were still there.
After inspecting the SQLite DB (shoud be the same for MySQL), I learned that
the file was deleted from the hard disk but the image info in the database was
not. The image is still in database with Album set to NULL and status set to

Thus, the trigger which removes the image properties was not activated.

This does not make any sense. Deleting an image from trash or directly should
also remove the entry from the images table.

Step to reproduce:
1) get the image id from some arbitrary image from the DB
2) add some image property for this image in the ImageProperties table
3) move the image to trash and delete it
The image id should still be in the DB

I inspected the source code. The imageviewutilities trigger the deletion of the
file via DIO but the deleteItem function of the core db class is not triggered.

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

More information about the Digikam-devel mailing list