[digikam] [Bug 376020] New: Moving of photos within the fuzzy search corrupts database

[bugzilla_noreply]

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

            Bug ID: 376020
           Summary: Moving of photos within the fuzzy search corrupts
                    database
           Product: digikam
           Version: 5.5.0
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Searches-Fuzzy
          Assignee: [hidden email]
          Reporter: [hidden email]
  Target Milestone: ---

I execute a fuzzy search to find duplicate photos. Photos are correctly
identified and shown in the result list. As the photos are in different folders
they are shown accordingly in the result list which is grouped by folder.

When I drag a photo onto the other to group them the GUI shows a correct
execution with the group icon. However, in the folders view the moved photo is
neither in the original nor in the destination folder though the counter of the
original folder is counting the photo. It seems that in the database the photo
has been moved but not in the file system. On linux level the photo is still in
the original folder.

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

[bugzilla_noreply]

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

Maik Qualmann <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #1 from Maik Qualmann <[hidden email]> ---
This behavior is actually correct. Grouped images are not moved but are only
linked in virtual form, the images remain in their original folders.

Maik

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

[bugzilla_noreply]

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

Mario Frank <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #2 from Mario Frank <[hidden email]> ---
Paul,
I second Maik. If you would move the image into the other folder, the image
would really be moved and vanish from source folder. Grouping is just an image
relation that is established.

This seems to me as a feature request in the way: Add option to group an image
to another image and move it to the same folder.

Is this what you expect?

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

[bugzilla_noreply]

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

Mario Frank <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Latest Commit|                            |https://commits.kde.org/dig
                   |                            |ikam/f58fc11f651c84cae37a75
                   |                            |8a40ec18be1229b8b1
   Version Fixed In|                            |5.5.0
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Mario Frank <[hidden email]> ---
Git commit f58fc11f651c84cae37a758a40ec18be1229b8b1 by Mario Frank.
Committed on 28/02/2017 at 13:02.
Pushed by mfrank into branch 'master'.

Added an option in context menu to group an image with another one and move it
to the album of the target image at the same time.
Though the problem described in 376020 is no bug, I think this use-case can
save users some work.
FIXED-IN: 5.5.0

M  +2    -1    NEWS
M  +26   -2    app/dragdrop/imagedragdrop.cpp

https://commits.kde.org/digikam/f58fc11f651c84cae37a758a40ec18be1229b8b1

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

[bugzilla_noreply]

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

Mario Frank <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Latest Commit|https://commits.kde.org/dig |https://commits.kde.org/dig
                   |ikam/f58fc11f651c84cae37a75 |ikam/c000a498d1776a52422069
                   |8a40ec18be1229b8b1          |15773c41497786fafe

--- Comment #4 from Mario Frank <[hidden email]> ---
Git commit c000a498d1776a5242206915773c41497786fafe by Mario Frank.
Committed on 28/02/2017 at 14:44.
Pushed by mfrank into branch 'master'.

If two root albums have the same name in file system, they are not
distinguishable as for both albums the header states Albums/albumnane.
But since all albums have a label, this one is better suited as albumname as
the user specifies the album himself.
FIXED-IN: 5.5.0

M  +2    -1    NEWS
M  +6    -1    libs/album/album.cpp
M  +13   -12   libs/album/album.h
M  +13   -0    libs/database/collection/collectionmanager.cpp
M  +6    -0    libs/database/collection/collectionmanager.h

https://commits.kde.org/digikam/c000a498d1776a5242206915773c41497786fafe

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

[bugzilla_noreply]

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

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Searches-Fuzzy              |Database-Similarity
                 CC|                            |[hidden email]

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