Skip to content

fix(search_library): match a query whose words span fields - #415

Merged
jeffcrouse merged 1 commit into
mainfrom
fix/search-library-words
Oct 25, 2026
Merged

jeffcrouse merged 1 commit into
mainfrom
fix/search-library-words

Conversation

@jeffcrouse

Copy link
Copy Markdown
Member

search_library required the whole query inside one field (ILIKE '%query%' on title, artist, album or genre). An MCP host naturally asks for " ", so "Inferno Boards of Canada" returned nothing on the NAS library, which holds all 18 tracks of that album. Found on 2026-10-25; "Evaporator Nathan Fake" failed the same way.

  • A multi-word query now also matches when every word appears in some field (an AND of per-word ORs). The whole-phrase match is kept, so single-field queries behave as before.
  • The tool description says so, so hosts know they can combine artist and album.
  • tests/test_search_library_words.py runs against the real test database: album+artist, either word order, a single phrase, and a non-matching word. The two spanning tests fail against the previous code.

Full backend suite: 2417 passed.

The 2-per-artist diversity cap, which hid Inferno when searching the artist alone, is unchanged; filter_tracks(artist=…) remains the tool for that.

🤖 Generated with Claude Code

The whole query had to appear inside one field, so "Inferno Boards of
Canada" found nothing on a library holding the album. A multi-word query
now also matches when every word appears in some field; a phrase in one
field still matches as before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jeffcrouse
jeffcrouse merged commit 1fed688 into main Oct 25, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant