Bug 318363 - Bad performance of file renames (thumbnail recreation?)
Summary: Bad performance of file renames (thumbnail recreation?)
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: AdvancedRename-file (show other bugs)
Version: 3.1.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-14 22:01 UTC by Frank Steinmetzger
Modified: 2022-01-31 21:57 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.2.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Steinmetzger 2013-04-14 22:01:58 UTC
Dear devs

I was just renaming a few dozen files in an album using the rename function. All I did was changing the extension to lower case, i.e. [name].[ext]{lower}. The process ran very slowly with a lot of HDD load. Apparently, the thumbnail is recreated for every image plus possibly some other database stuff (I saw the thumbnail DB grow while renaming was in progress).
From my point of view, should a simple changing of the filename reference in the database not be enough instead of creating a whole new image entry?

Thanks for your consideration.

Reproducible: Always

Steps to Reproduce:
Rename a bunch of files.
Actual Results:  
It takes quite some time and causes a lot of disk load.

Expected Results:  
It should be quite fast, because basically only one string should be changed in the database.
Comment 1 Frank Steinmetzger 2013-09-14 20:42:31 UTC
This seems to be related to #305359. I'm using SQLite by the way.

*** This bug has been marked as a duplicate of bug 305359 ***
Comment 2 caulier.gilles 2020-09-12 10:52:03 UTC
Fixed with #305359