BoulderBadgeDad 776afdd1fd video enrichment: survive legacy UNIQUE on tmdb_id/tvdb_id (no scan crash) ... Existing DBs created before the schema dropped UNIQUE still have shows.tvdb_id / movies.tmdb_id UNIQUE, so enrichment matching two items to the same id threw 'UNIQUE constraint failed' repeatedly. enrichment_apply now catches the IntegrityError and retries without the id columns — keeps the existing (authoritative) id and still records match_status + metadata. Non-destructive (no table rebuild). Test simulates the legacy unique index.		2026-06-14 12:34:52 -07:00
..
__init__.py	basic db structure	2025-08-05 22:43:04 -07:00
music_database.py	M3U export: resolve paths via one bulk read instead of a per-artist search loop (fixes 'Export M3U hangs forever' under active enrichment/scan DB writes)	2026-06-13 08:55:46 -07:00
personalized_schema.py	Personalized pipeline: auto-refresh stale snapshots after watchlist scan	2026-05-15 20:53:03 -07:00
video_database.py	video enrichment: survive legacy UNIQUE on tmdb_id/tvdb_id (no scan crash)	2026-06-14 12:34:52 -07:00
video_schema.sql	video enrichment 1a: DB layer (match-status cols + migration + helpers)	2026-06-14 11:18:46 -07:00