From 75b2a349ebd6fada5cbc92bfae9854cc2cd53c63 Mon Sep 17 00:00:00 2001 From: Caleb Allen Date: Mon, 9 Mar 2026 10:48:11 -0400 Subject: [PATCH] fix(10-01): move library_id index to migration 6 to fix existing DB startup On existing databases, CREATE TABLE IF NOT EXISTS audio_files is a no-op but the standalone CREATE INDEX on library_id would fail because the column doesn't exist until migration 6 runs. The migration already creates this index, so removing it from the schema file is correct. --- backend/database/sql/schemas/audio_files.sql | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/backend/database/sql/schemas/audio_files.sql b/backend/database/sql/schemas/audio_files.sql index 29489da..673294f 100644 --- a/backend/database/sql/schemas/audio_files.sql +++ b/backend/database/sql/schemas/audio_files.sql @@ -19,5 +19,6 @@ CREATE TABLE IF NOT EXISTS audio_files ( CREATE INDEX IF NOT EXISTS idx_audio_files_recording_id ON audio_files(recording_id); -CREATE INDEX IF NOT EXISTS idx_audio_files_library_id - ON audio_files(library_id); +-- idx_audio_files_library_id is created by migration 6 (not here) because +-- on existing databases this schema file is a no-op (CREATE TABLE IF NOT EXISTS) +-- and the library_id column doesn't exist until the migration adds it.