bvandeusenandClaude Opus 5.5 598abeb8cf fix: a fresh app install syncs the whole library, not the last 30 days of changes (#6778) ...

The change feed dropped every row older than 30 days, and an app syncing
from cursor 0 builds its library from the feed, so a fresh install, cleared
data or a 410 reset got only what had changed lately.

The compactor now keeps each entity's latest change however old. It drops a
row once a newer one for the same entity exists, and a delete once it is 30
days old, raising a stored mark (library_changes_trimmed) past it; an app
whose cursor is below the mark is sent back to 0, as before. Migration 0101
adds the index the compactor needs, seeds the mark where the old compactor
left off, and gives every artist, album and track whose latest row is not an
upsert a fresh one, so the rows the old compactor dropped come back. The
backup carries the mark with the feed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-11-02 22:07:42 -05:00

..

acoustid.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

acquisition.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

admin_status.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

admin_summary.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

albums.sql.go

feat(subsonic): getAlbumList2 recent and frequent read the caller's play history (#6293)

2026-10-23 13:58:09 -04:00

artists.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

audit_log.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

backups.sql.go

feat: the backup can include the music, sending each library file once to music/ and again only when it changes (#6774)

2026-11-02 15:26:20 -05:00

browse.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

candidate_artist_tags.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

catalogue.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

contextual_likes.sql.go

feat(db): add lidarr_config + lidarr_requests schema (migration 0010)

2026-04-29 15:10:01 -04:00

coplay.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

coverart_settings.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

covers.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

db.go

feat(db): add lidarr_config + lidarr_requests schema (migration 0010)

2026-04-29 15:10:01 -04:00

diagnostics.sql.go

feat(server/diagnostics): device debug-reporting ingest + admin timeline + retention (M9)

2026-06-29 18:38:56 -04:00

discover.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

duplicates.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

events.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

fingerprint_settings.sql.go

feat: duplicates resolve themselves where Lidarr says it is safe (M498)

2026-10-08 21:49:37 -04:00

fingerprints.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

gc.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

history.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

imports.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

invites.sql.go

feat(db/m7-user-mgmt): migration 0022 + audit helper

2026-05-07 11:51:00 -04:00

library_changes.sql.go

fix: a fresh app install syncs the whole library, not the last 30 days of changes (#6778)

2026-11-02 22:07:42 -05:00

library_settings.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

lifecycle.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

likes.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

loudness.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

merge.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

missing_pairs.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

models.go

fix: a fresh app install syncs the whole library, not the last 30 days of changes (#6778)

2026-11-02 22:07:42 -05:00

network_settings.sql.go

fix(auth): build password-reset links from an operator-set public address, never the Host header (M462 #4981)

2026-10-06 09:32:10 -04:00

normalization_prefs.sql.go

feat: per-user volume leveling preference, synced across devices (M464 #4998)

2026-10-06 14:29:40 -04:00

notifications.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

password_resets.sql.go

feat(db/m7-user-mgmt): migration 0024 + self-service + SMTP queries (U3)

2026-05-07 12:34:44 -04:00

playback_errors.sql.go

feat: notifications say what changed and alert once: a grouped notice names the tracks, grows without re-alerting, and a phone pile lists its titles (M542 #6146-#6151)

2026-10-19 22:44:19 -04:00

playlists.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

quarantine.sql.go

feat: Minstrel no longer talks to Lidarr: its connection, Delete via Lidarr and the unmonitor options are gone, and the track reports are plain quarantine (M502 #5525)

2026-10-11 13:48:20 -04:00

reacquisition.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

recommendation_metrics.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

recommendation_tuning.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

recommendation.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

registration_settings.sql.go

feat(db/m7-user-mgmt): migration 0022 + audit helper

2026-05-07 11:51:00 -04:00

requests.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

scan_runs.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

scrobble.sql.go

feat(db): add lidarr_config + lidarr_requests schema (migration 0010)

2026-04-29 15:10:01 -04:00

search.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

sessions.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

similarity.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

smtp_config.sql.go

feat(db/m7-user-mgmt): migration 0024 + self-service + SMTP queries (U3)

2026-05-07 12:34:44 -04:00

songs.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

suggestion_snoozes.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

system_mixes.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

system_playlist_rotation.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

system_playlists.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

tag_settings.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

taste_profile.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

track_tags.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

tracks.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

users.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

wanted.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00

you_might_like.sql.go

docs: query comments say what each query selects and why, not how it came to be (#6277)

2026-10-23 12:31:13 -04:00