starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-07-16 05:43:54 +03:00
Code Issues 822 Packages Projects Releases 17 Wiki Activity

[PR #2478] [MERGED] Fix ordering of search results #9127

New Issue
Closed
opened 2026-02-07 05:56:41 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-07 05:56:41 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/jellyfin/jellyfin/pull/2478
Author: @JustAMan
Created: 2/28/2020
Status: ✅ Merged
Merged: 3/22/2020
Merged by: @dkanada

Base: master ← Head: fix-search-order

📝 Commits (2)

📊 Changes

1 file changed (+19 additions, -18 deletions)

View changed files

📝 Emby.Server.Implementations/Data/SqliteItemRepository.cs (+19 -18)

📄 Description

Changes

Try to make search make more sense. At least make it so items which names start with what you searched for are in the front of the list.
It also sorts by SortName column, which implementations for audio and episodes are questionable for search, but it's still better than current situation, where search results would end up being in undefined (DB-dependent) order.

Issues

Not sure, maybe there are some.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/jellyfin/jellyfin/pull/2478 **Author:** [@JustAMan](https://github.com/JustAMan) **Created:** 2/28/2020 **Status:** ✅ Merged **Merged:** 3/22/2020 **Merged by:** [@dkanada](https://github.com/dkanada) **Base:** `master` ← **Head:** `fix-search-order` --- ### 📝 Commits (2) - [`a9f3b5d`](https://github.com/jellyfin/jellyfin/commit/a9f3b5dacbd67ac9df65c5b7bbeef159bbb40aa7) Fix ordering of search results - [`7270997`](https://github.com/jellyfin/jellyfin/commit/7270997e768a7ceec391809f8185b5d08ff249bb) add code suggestions ### 📊 Changes **1 file changed** (+19 additions, -18 deletions) <details> <summary>View changed files</summary> 📝 `Emby.Server.Implementations/Data/SqliteItemRepository.cs` (+19 -18) </details> ### 📄 Description <!-- Ensure your title is short, descriptive, and in the imperative mood (Fix X, Change Y, instead of Fixed X, Changed Y). For a good inspiration of what to write in commit messages and PRs please review https://chris.beams.io/posts/git-commit/ and our documentation. --> **Changes** <!-- Describe your changes here in 1-5 sentences. --> Try to make search make more sense. At least make it so items which names _start_ with what you searched for are in the front of the list. It also sorts by `SortName` column, which implementations for audio and episodes are questionable for search, but it's still better than current situation, where search results would end up being in undefined (DB-dependent) order. **Issues** <!-- Tag any issues that this PR solves here. ex. Fixes # --> Not sure, maybe there are some. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-07 05:56:41 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#9127
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?