Files
minstrel/internal/db/migrations/0089_library_match_by_hand.up.sql
bvandeusenandClaude Opus 5.5 a8786abace
release / govulncheck (push) Successful in 16s
release / web (push) Successful in 1m17s
release / go (push) Successful in 1m34s
release / integration (push) Failing after 5m34s
release / android (push) Successful in 5m36s
release / Build signed APK (releases and dev) (push) Successful in 5m44s
release / Attach APK to the Release (tag releases only) (push) Skipped
release / Build + push container image (push) Skipped
release / Verify release artifacts (tag releases only) (push) Skipped
feat: Collection › Unmatched lists the library albums no MusicBrainz album matched, each matched by hand from a search or a link, or left off (M502 #5579)
Like Lidarr's Unmapped Files. A local band's album, which MusicBrainz will
never have, is left off: never matched again and not counted. A re-tagged
album is matched again on the next listing. The Collection's verdict now
says when library albums need matching.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-10 22:12:30 -04:00

11 lines
775 B
SQL

-- The Collection's Unmatched section (#5579): a person matches an album the
-- listing could not, by a MusicBrainz link or a search (method 'manual'),
-- or leaves it off the list for good (outcome 'dismissed': a local band's
-- album MusicBrainz will never have, a mix that is no album).
ALTER TABLE library_album_matches DROP CONSTRAINT library_album_matches_outcome_check;
ALTER TABLE library_album_matches ADD CONSTRAINT library_album_matches_outcome_check
CHECK (outcome IN ('listed', 'unmatched', 'dismissed'));
ALTER TABLE library_album_matches DROP CONSTRAINT library_album_matches_method_check;
ALTER TABLE library_album_matches ADD CONSTRAINT library_album_matches_method_check
CHECK (method IN ('', 'tags', 'release', 'discography', 'search', 'manual'));