Re: "scan for new items" always scans the entire collection

Paul Moles <[email protected]> Thu, 9 Jul 2026 08:27:35 +0100
Newsgroups gmane.comp.kde.digikam.user
Message-ID <AS5P195MB33801A0D09DF8F7729CE5503DAFE2@AS5P195MB3380.EURP195.PROD.OUTLOOK.COM>
Similar experience, basic set up on  Windows 11, Digikam 9.1.0

Driving my HDD crazy at every start up.

Cheers

Paul

On 09/07/2026 06:33, VALÍK Robert wrote:
> Hey there!
>
> After upgrading Digikam to version 9.1, I have also noticed this weird 
> behavior.
>
> I have:
>
> - EndeavourOS
> - extra/digikam 9.1.0-4 (32.9 MiB 115.2 MiB) (Installed)
> - MariaDB server as a backend
>
> Config:
>
> - "Scan for new items at startup" on
> - "Fast Scan (...)" on
>
> I have had this configuration for years (the Digikam DB may have 
> worked and been upgraded for about 10 years). Up until upgrade - every 
> time I have started Digikam, it scanned briefly (like seconds) for new 
> items, if there were new items, it imported them (few seconds or 
> minutes) and so.
>
> But after upgrading, it scans and updates the entire collection every 
> time. It takes more than 8hrs. Digikam rewrites all data stored in the 
> database. It creates like 3GB of binlogs every time. If I log queries, 
> it literally checks timestamp of a picture and than deletes and writes 
> it's metadata (and thumbnails) all over again. After it finishes and I 
> close it and start again, it happens again.
>
> I have tried every DB maintenance option I have found in Digikam, 
> still not working properly.
>
> The only thing that did help - was to migrate the DB to SQLite (this 
> is complicates things for me, as I synchronize images and metadata 
> from Digikam to my webpage and SQLite cannot be as effectively backed 
> up as MariaDB...).
>
> It seems like Digikam may not be handling timestamps stored in MariaDB 
> properly and decides that the metadata meed to be updated or something.
>
> Robert