https://bugs.kde.org/show_bug.cgi?id=431096
Bug ID: 431096
Summary: Adding new collection scans all existing collections
for new items
Product: digikam
Version: 7.1.0
Platform: Other
OS: Microsoft Windows
Status: REPORTED
Severity: minor
Priority: NOR
Component: Database-Scan
Assignee: digikam-bugs-n...@kde.org
Reporter: sven.burmeis...@gmx.net
Target Milestone: ---
SUMMARY
If one adds a new (network) collection, digikam scans all (network [I only have
network collections]) collections for new items before actually adding the new
(network) collection to the albums view.
STEPS TO REPRODUCE
1. Have a large (network) collection (to make the effect visible)
2. Add a new (network) collection (in my case the first letter of the
collection foldername is further in the alphabet compared to the existing
collection, i.e. existing: Axxxxx, new Bxxxx, if that matters)
3. Check the scanning process and the albums view
OBSERVED RESULT
Looking at the logs of the server, digikam starts to scan the already existing
collection Axxx.
The new collection does not appear in the albums view until digikam has
finished scanning the "old" collection Axxx and starts scanning the new
collection Bxxx. In my case it takes literally ours scanning the "old"
collection which made me think that digikam is stuck when adding a new network
collection, since the scanning process remained at 0% for more than 10 minutes.
EXPECTED RESULT
Only scan for new items in the newly added collection.
SOFTWARE/OS VERSIONS
Windows: 10
ADDITIONAL INFORMATION
I set this bug to minor since digikam works and one does not add new
collections every day. However, for people with large network collections this
is a pretty time consuming/major bug.
If it matters:the network collections are on the same network drive (Z:), but
ecist in different folders. The network drive is a Windows webdav network drive
that points to a Nextcloud server.
--
You are receiving this mail because:
You are watching all bug changes.
