https://bugs.kde.org/show_bug.cgi?id=397901
--- Comment #3 from Pete Hall <p...@hallcircus.net> --- After storing a certain number (unknown but less then 32767, so not a data type issue) of images, digikam cannot display the number of images in a directory (it always shows zero) for most recently added directories (ONLY MOST RECENT DIRECTORIES). Images in directories that show zero items in digikam, do not appear as thumbnails, and cannot be retrieved for viewing or editing. This can be worked around by splitting up images into two groups so you never reach that magic number of images. Splitting up images means that you must store part of your total image catalog on a different file system, and must umount it. If both parts are mounted at the same time, you exceed that magic number of images across all file systems, and the problem re-appears. I can do this umounting and mounting externally to digikam, and this works, but is not very user friendly. Also cannot move images from the mounted group to the umounted group, which is even more user un-friendly. By the way, I have tried moving to mariadb. maybe that will solve the problem eventually, but cannot get mariadb to work on ubuntu 18.04 due to dependency version mismatches in the ubuntu repository. I do not want to violate this due to unknown side effects with other packages. The problem may not be the database anyway. Maybe it is caused by a maximum number of objects allowed in a java collection or something like that. This I cannot determine. -- You are receiving this mail because: You are watching all bug changes.
