austinried 06ca2da48d add frequently and recently played album and artist sorts ...

Song playCount/played are parsed and synced, then aggregated per album
(SUM/MAX) and per artist (through the album's artistId) after the song
sync. Albums and artists gain Frequent/Recent sorts with their own
indices; the options show only when the active source returned the
fields, and the aggregate only writes rows whose value changed.

The artist subqueries pin index_albums_sourceId_artistId: without it the
planner answers MAX(played) from index_albums_recent (sourceId, played),
which cannot apply the artistId equality, and scans every album once per
artist. The availability flows read the indexed album ranks rather than
scanning songs, which would re-run on every song-sync batch.

2026-10-04 00:30:05 +00:00

..

config

show the app's own GPL-3.0 licence and the bundled public suffix list

2026-10-04 00:30:05 +00:00

schemas/com.subtracks.data.db.SubtracksDatabase

add frequently and recently played album and artist sorts

2026-10-04 00:30:05 +00:00

src

add frequently and recently played album and artist sorts

2026-10-04 00:30:05 +00:00

build.gradle.kts

address review: join the controller scope, keep DB closes where nothing leaks

2026-10-04 00:30:05 +00:00