Listings matched children on four columns at once (parent_id, album_id,
season_id, series_id) because Jellyfin's ParentId is the storage parent,
not the logical one. The OR defeated the planner into a full scan, and it
was wrong: every episode carries its series id, so a series listed all its
episodes beside its seasons (on both the browse and Downloads surfaces).
- Migration 027 adds items.container_id, a VIRTUAL generated column
(episode -> season/series/parent, season -> series, track -> album,
else parent) indexed with (sort_name, name), so a listing is one
ordered index range and every write path is covered untouched.
- Containers never cached (an episode that arrived via Next Up) get
placeholders named from the child's own fields, in the migration and
on every cache write, so offline navigation stays series -> season.
- The six queries that built the set of every downloaded item in a CTE
(get_item, latest, recently played, search, favourites, by-person,
Downloads) now check availability per row with one shared predicate.
- PRAGMA optimize at open gives the planner statistics.
Benchmark (~110k items, desktop): series listing ~80 ms -> <1 ms;
migration 027 upgrades that database in ~0.1 s (0.2 s on the Fairphone).
Tests first: a series listing its episodes, and the Downloads series
drill, both failed before the change.
dtourolle
c0545a245f