q in digiKam 8.5 Appimage

[Dr. A. Krebs]

Dear:

I handle quite a large number of pics in my collections. Handling 
several sub-collections is slow and edgy, takes much timne and is faulty!!

*digiKam offers three paths*:


1.) local collections

2.) collectionbs on removable media (USB, e.g.)

3.) collections on network-based media (NAS, e.g.)


The installation (databases) are located on a fast SSD drive with some 
200 GB space. Right now, thumbnails-digikam have some 60 GB size; for no 
known reason, digiKam would not restart and work again.

Aside, new recognising all files takes 4 to 7 days to finish!! On a 
SSD-drive!?

I mean, only reading, not reorganising, I guess, this is not reasonable 
any more.


*IDEA*:

 From an mathematical (statistical) sight, it would be extremely 
advantageous to threat *every path independently*- limited risk to loose 
the complete database.

Instead, potential risk to damage (loose) would extend only(!!) to the 
files associated to one single path.

So, for local digiKam4.db, recognition.db, similarity.db, 
thumbnails-digikam.de plus their -shm /db-wal associates.


*Even more consequent*, it would be most promising to uses this 
independency for every user-selected directory. Reason: some of my 
(sub-)directories have several hundred of thousands of pics.

I believe this measure would contribute much to further stabilise usage 
of digiKam even under worst case scenarios.

Hope you agree?


Best Axel

-- 

MX LINUX 23.4, (debian based)

16 GB RAM