Add prefix search to search by internal DB ID#1856
Merged
AntsyLich merged 2 commits intomihonapp:mainfrom Mar 13, 2025
Merged
Conversation
This prefix searches entries in the library based on the ID in the database. It is a niche feature but could be very helpful in certain situations, such as a corrupted cover causing a crash that just shows "🚨 Failed - MangaCover(mangaId=2245, sourceId=1, isMangaFavorite=true, url=, lastModified=0)". With this prefix search it is possible to find the entry in question without much hassle. Notably, the database includes literally anything Mihon has ever seen from extension and such, even if they weren't added to the collection. This means that IDs actually present in the collection are not expected to be purely sequential. For example, in my emulator, I had two entries in the collection but the assigned IDs were 5 and 56.
cuong-tran
pushed a commit
to komikku-app/komikku
that referenced
this pull request
Mar 22, 2025
This prefix searches entries in the library based on the ID in the database. It is a niche feature but could be very helpful in certain situations, such as a corrupted cover causing a crash that just shows "🚨 Failed - MangaCover(mangaId=2245, sourceId=1, isMangaFavorite=true, url=, lastModified=0)". With this prefix search it is possible to find the entry in question without much hassle. Notably, the database includes literally anything Mihon has ever seen from extension and such, even if they weren't added to the collection. This means that IDs actually present in the collection are not expected to be purely sequential. For example, in my emulator, I had two entries in the collection but the assigned IDs were 5 and 56. (cherry picked from commit 05012de)
cuong-tran
pushed a commit
to komikku-app/komikku
that referenced
this pull request
Mar 23, 2025
This prefix searches entries in the library based on the ID in the database. It is a niche feature but could be very helpful in certain situations, such as a corrupted cover causing a crash that just shows "🚨 Failed - MangaCover(mangaId=2245, sourceId=1, isMangaFavorite=true, url=, lastModified=0)". With this prefix search it is possible to find the entry in question without much hassle. Notably, the database includes literally anything Mihon has ever seen from extension and such, even if they weren't added to the collection. This means that IDs actually present in the collection are not expected to be purely sequential. For example, in my emulator, I had two entries in the collection but the assigned IDs were 5 and 56. (cherry picked from commit 05012de)
cuong-tran
pushed a commit
to komikku-app/anikku
that referenced
this pull request
May 31, 2025
This prefix searches entries in the library based on the ID in the database. It is a niche feature but could be very helpful in certain situations, such as a corrupted cover causing a crash that just shows "🚨 Failed - MangaCover(mangaId=2245, sourceId=1, isMangaFavorite=true, url=, lastModified=0)". With this prefix search it is possible to find the entry in question without much hassle. Notably, the database includes literally anything Mihon has ever seen from extension and such, even if they weren't added to the collection. This means that IDs actually present in the collection are not expected to be purely sequential. For example, in my emulator, I had two entries in the collection but the assigned IDs were 5 and 56. (cherry picked from commit 05012de569130e131be92b71fbfc9308ea6c629c)
Ramsesdb
pushed a commit
to Ramsesdb/gexu-legacy-fork
that referenced
this pull request
Jan 19, 2026
This prefix searches entries in the library based on the ID in the database. It is a niche feature but could be very helpful in certain situations, such as a corrupted cover causing a crash that just shows "🚨 Failed - MangaCover(mangaId=2245, sourceId=1, isMangaFavorite=true, url=, lastModified=0)". With this prefix search it is possible to find the entry in question without much hassle. Notably, the database includes literally anything Mihon has ever seen from extension and such, even if they weren't added to the collection. This means that IDs actually present in the collection are not expected to be purely sequential. For example, in my emulator, I had two entries in the collection but the assigned IDs were 5 and 56.
yechika
pushed a commit
to yechika/mihon
that referenced
this pull request
Apr 27, 2026
This prefix searches entries in the library based on the ID in the database. It is a niche feature but could be very helpful in certain situations, such as a corrupted cover causing a crash that just shows "🚨 Failed - MangaCover(mangaId=2245, sourceId=1, isMangaFavorite=true, url=, lastModified=0)". With this prefix search it is possible to find the entry in question without much hassle. Notably, the database includes literally anything Mihon has ever seen from extension and such, even if they weren't added to the collection. This means that IDs actually present in the collection are not expected to be purely sequential. For example, in my emulator, I had two entries in the collection but the assigned IDs were 5 and 56.
Ramsesdb
pushed a commit
to Ramsesdb/gexu-legacy-fork
that referenced
this pull request
May 6, 2026
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Ramsesdb
pushed a commit
to Ramsesdb/gexu-legacy-fork
that referenced
this pull request
May 6, 2026
This prefix searches entries in the library based on the ID in the database. It is a niche feature but could be very helpful in certain situations, such as a corrupted cover causing a crash that just shows "🚨 Failed - MangaCover(mangaId=2245, sourceId=1, isMangaFavorite=true, url=, lastModified=0)". With this prefix search it is possible to find the entry in question without much hassle. Notably, the database includes literally anything Mihon has ever seen from extension and such, even if they weren't added to the collection. This means that IDs actually present in the collection are not expected to be purely sequential. For example, in my emulator, I had two entries in the collection but the assigned IDs were 5 and 56. (cherry picked from commit 05012de)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This prefix searches entries in the library based on the ID in the database. It is a niche feature but could be very helpful in certain situations, such as a corrupted cover causing a crash in Coil that just shows
🚨 Failed - MangaCover(mangaId=2245, sourceId=1, isMangaFavorite=true, url=, lastModified=0). With this prefix search it is possible to find the entry in question without much hassle.Notably, the database includes literally anything Mihon has ever seen from extension and such, even if they weren't added to the collection. This means that IDs actually present in the collection are not expected to be purely sequential.
For example, in my emulator, I had two entries in the collection but the assigned IDs were 5 and 56.