Postgres recomputed a tsvector over every article's full text on every
search. A migration now adds a stored, GIN-indexed search_vector column
kept current by a trigger (so no ingest/update path can forget it), and
the backend reads that column. Untested here: no Postgres in the dev
sandbox, so the SQL is reviewed but not executed — worth one run of the
(skipped-on-SQLite) Postgres test module against a real instance.
SQLite search built one bound parameter per subscribed feed, so enough
feeds would exceed the variable limit, and the OperationalError was
swallowed into "no results". It now scopes through a subquery on
Subscription and logs failures. SQLite connections also get WAL mode,
a 20s busy timeout, and IMMEDIATE transactions so gunicorn, Celery, and
the FTS triggers stop tripping over each other.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Implements the backend-agnostic search interface from the plan,
selected at runtime by connection.vendor:
- SQLite: an FTS5 virtual table (external-content, mirroring
Article.title/content_html) created via a vendor-conditional
migration, kept in sync by insert/update/delete triggers. Queries
wrap the whole user input as a single FTS5 phrase so punctuation in
a search box can't break MATCH syntax. `reindex_search` management
command rebuilds it after bulk imports.
- Postgres: computes the search vector on the fly per the plan's
decision (title weighted above content, no stored/indexed column)
rather than diverging the schema from SQLite.
Both backends scope results to the requesting user's own subscriptions
and share the stream/detail article-row template and read/star/save
actions via a new apps.articles.queries.with_user_state() helper,
extracted from apps.reader.views to avoid duplicating that annotation
logic for search results.
Verified live: the SQLite path end-to-end in-browser against the real
Hacker News subscription (search UI, phrase matching, no-match case),
and the Postgres path against a throwaway Postgres container (search,
feed-scoping, and title-vs-content ranking), torn down afterward — not
part of this project's own infrastructure.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>