| Summary: | Incorrect display of album thumbnails | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Peter <benedekppeter> |
| Component: | Thumbs-Album | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 7.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/graphics/digikam/commit/56c96d9aadca8a2108c08b09888541e52a0eedea | Version Fixed/Implemented In: | 7.5.0 |
| Sentry Crash Report: | |||
|
Description
Peter
2021-12-19 14:48:19 UTC
Example database and an Screenshot in the zip archivum: https://mega.nz/file/EN40xCAC#pb0oZO-ebqBuZV84eNwh40Um_fImolLYVIbvb50kAQQ Sorry, an important info missed: "I attached it to the ticket a database dump file and..." Correctly: I attached it to the ticket a MYSQL database dump file and... Well the problem is not unknown. The problem occurs when the item identifier is duplicated in the view model. In principle, we've fixed almost all of the problems over the years. The item identifier is formed from the file path in your settings, I see a very long path, there must be duplicate identifications. I'll have a look. Maik The SQL dump is very helpful, I can reproduce the problem. The cause is the identifier for the item separation by album, the other as format and month do not have the problem. Maik > I see a very long path
Yes, the girls in the office used very long file path in the past. This is a difficult legacy. :-(
Ok, you have another problem. In your collection you have album paths that only differ in upper / lower case, that is currently not possible with MySQL, see also Bug 414344. Change the following album names: /Dokumentumok/Pályázatok/LEADER/tuskevar (tuskevar exists also in upper case) /_BACKUP_/20190928_6_12_duplikatum/X/Dokumentumok/Pályázatok/Pályázatok/ÚJ LEADERES PÁLYÁZATOK/Jeles napok a Szentek társaságában/DOKUMENTUMOK/dokumentáció/2013.10.18 - Növények a Bibliából - Kertbarátkör előadás/fotódokumentáció /_BACKUP_/20191001_4_5_duplikatum/X/Dokumentumok/Pályázatok/2016/Alapítvány/Norvég Alap/Loli Zumi/Szakmai előrehaladási jelentés/3. Szakmai előrehaladási jelentés Loli Zumi/Alátámasztó dokumentumok/Szakmai tevékenység megvalósításába bevont közreműködők Maik (In reply to Maik Qualmann from comment #6) > Ok, you have another problem. In your collection you have album paths that > only differ in upper / lower case, that is currently not possible with > MySQL, see also Bug 414344. > > Change the following album names: > > /Dokumentumok/Pályázatok/LEADER/tuskevar (tuskevar exists also in upper > case) > > /_BACKUP_/20190928_6_12_duplikatum/X/Dokumentumok/Pályázatok/Pályázatok/ÚJ > LEADERES PÁLYÁZATOK/Jeles napok a Szentek > társaságában/DOKUMENTUMOK/dokumentáció/2013.10.18 - Növények a Bibliából - > Kertbarátkör előadás/fotódokumentáció > > /_BACKUP_/20191001_4_5_duplikatum/X/Dokumentumok/Pályázatok/2016/Alapítvány/ > Norvég Alap/Loli Zumi/Szakmai előrehaladási jelentés/3. Szakmai > előrehaladási jelentés Loli Zumi/Alátámasztó dokumentumok/Szakmai > tevékenység megvalósításába bevont közreműködők > > Maik Long filenames and exotic characters in the names. I knew they were going to cause a problem now or later... I will change the path and filenames. Thank You Maik. Regards Peter Since the problem occurs more often in bug 414344, I plan to convert the columns Albums:relativePath and Images:name in MySQL as collate utf8-bin. Then album paths and file names can only differ in upper / lower case even under MySQL. Maik Fixed with commit: https://invent.kde.org/graphics/digikam/-/commit/56c96d9aadca8a2108c08b09888541e52a0eedea Maik Git commit 56c96d9aadca8a2108c08b09888541e52a0eedea by Maik Qualmann. Committed on 20/12/2021 at 07:16. Pushed by mqualmann into branch 'master'. use COLLATE utf8_bin for album path and image name Related: bug 414344, bug 435767, bug 445948 FIXED-IN: 7.5.0 M +4 -4 NEWS M +11 -2 core/data/database/dbconfig.xml.cmake.in M +9 -1 core/libs/database/coredb/coredbschemaupdater.cpp https://invent.kde.org/graphics/digikam/commit/56c96d9aadca8a2108c08b09888541e52a0eedea (In reply to Maik Qualmann from comment #10) > Git commit 56c96d9aadca8a2108c08b09888541e52a0eedea by Maik Qualmann. > Committed on 20/12/2021 at 07:16. > Pushed by mqualmann into branch 'master'. > > use COLLATE utf8_bin for album path and image name > Related: bug 414344, bug 435767, bug 445948 > FIXED-IN: 7.5.0 > > M +4 -4 NEWS > M +11 -2 core/data/database/dbconfig.xml.cmake.in > M +9 -1 core/libs/database/coredb/coredbschemaupdater.cpp > > https://invent.kde.org/graphics/digikam/commit/ > 56c96d9aadca8a2108c08b09888541e52a0eedea This excellent news! Thanks Maik! In this case, do I need to rebuild the database? Or, what should I do? A database update is then carried out automatically when digiKam starts. The start scan for new items will then find additional folders and possibly images that previously only differed in upper / lower case. The problem with the view should then be resolved. With this commit we have already made sure that the search for album path and item name is still not case sensitive. https://invent.kde.org/graphics/digikam/-/commit/7c06a091903978bd698067a5b93875f36653a913 Maik Ok! Grateful thanks Maik! |