BoulderBadgeDad 5e8143dd1d video scan: survive legacy UNIQUE on tmdb_id/tvdb_id (store the row, drop the dup id) ... Existing DBs created movies.tmdb_id / shows.tvdb_id as inline UNIQUE (can't be dropped via migration). The new model allows the same title in >1 library, so a second movie/show with the same id raised IntegrityError and the scanner SKIPPED it — dropping the title (observed: 'UNIQUE constraint failed: movies.tmdb_id', movie 548522 skipped). upsert_movie/upsert_show_tree now use a shared _resilient_upsert: on IntegrityError, retry WITHOUT the id columns so the row is stored (just without the colliding id) — same pattern enrichment_apply already used. Regression tests for both movies and shows under a simulated legacy unique index.		2026-06-14 17:33:38 -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 scan: survive legacy UNIQUE on tmdb_id/tvdb_id (store the row, drop the dup id)	2026-06-14 17:33:38 -07:00
video_schema.sql	video 'capture everything' (phase 1): stills, genres, ratings, tagline	2026-06-14 17:17:20 -07:00