#9 Major routes refactor and expansion, #15 Added API for statistics, Added search cache backend and functionality tests, Backend sync improvements

internal/db/migrations/000005_rename_game_to_soundtrack.down.sql

@@ -1,33 +0,0 @@
--- Revert: Rename soundtrack table back to game
-ALTER TABLE soundtrack RENAME TO game;
-
--- Revert primary key sequence
-ALTER SEQUENCE soundtrack_id_seq RENAME TO game_id_seq;
-
--- Revert columns in game table
-ALTER TABLE game RENAME COLUMN soundtrack_name TO game_name;
-
--- Revert song table: rename soundtrack_id back to game_id
-ALTER TABLE song RENAME COLUMN soundtrack_id TO game_id;
-
--- Revert song primary key
-ALTER TABLE song DROP CONSTRAINT IF EXISTS song_pkey;
-ALTER TABLE song ADD PRIMARY KEY (game_id, path);
-ALTER TABLE song RENAME CONSTRAINT song_pkey_soundtrack TO song_pkey;
-
--- Revert song_list table references
-ALTER TABLE song_list RENAME COLUMN soundtrack_name TO game_name;
-
--- Revert foreign key constraint
-ALTER TABLE song DROP CONSTRAINT IF EXISTS song_soundtrack_id_fkey;
-ALTER TABLE song ADD CONSTRAINT song_game_id_fkey 
-    FOREIGN KEY (game_id) REFERENCES game(id);
-
--- Revert indexes
-ALTER INDEX IF EXISTS idx_soundtrack_deleted RENAME TO idx_game_deleted;
-ALTER INDEX IF EXISTS idx_soundtrack_hash RENAME TO idx_game_hash;
-ALTER INDEX IF EXISTS idx_soundtrack_path RENAME TO idx_game_path;
-ALTER INDEX IF EXISTS idx_soundtrack_name RENAME TO idx_game_name;
-ALTER INDEX IF EXISTS idx_song_soundtrack_id RENAME TO idx_song_game_id;
-ALTER INDEX IF EXISTS idx_song_soundtrack_id_song_name RENAME TO idx_song_game_id_song_name;
-ALTER INDEX IF EXISTS song_list_soundtrack_name_idx RENAME TO song_list_game_name_idx;

internal/db/migrations/000005_rename_game_to_soundtrack.up.sql

@@ -1,32 +0,0 @@
--- Rename game table to soundtrack
-ALTER TABLE game RENAME TO soundtrack;
-
--- Rename primary key sequence
-ALTER SEQUENCE game_id_seq RENAME TO soundtrack_id_seq;
-
--- Rename columns in soundtrack table
-ALTER TABLE soundtrack RENAME COLUMN game_name TO soundtrack_name;
-
--- Update song table: rename game_id to soundtrack_id
-ALTER TABLE song RENAME COLUMN game_id TO soundtrack_id;
-
--- Update song primary key
-ALTER TABLE song DROP CONSTRAINT IF EXISTS song_pkey;
-ALTER TABLE song ADD PRIMARY KEY (soundtrack_id, path);
-
--- Update song_list table references
-ALTER TABLE song_list RENAME COLUMN game_name TO soundtrack_name;
-
--- Rename foreign key constraint
-ALTER TABLE song DROP CONSTRAINT IF EXISTS song_game_id_fkey;
-ALTER TABLE song ADD CONSTRAINT song_soundtrack_id_fkey 
-    FOREIGN KEY (soundtrack_id) REFERENCES soundtrack(id);
-
--- Rename indexes
-ALTER INDEX IF EXISTS idx_game_deleted RENAME TO idx_soundtrack_deleted;
-ALTER INDEX IF EXISTS idx_game_hash RENAME TO idx_soundtrack_hash;
-ALTER INDEX IF EXISTS idx_game_path RENAME TO idx_soundtrack_path;
-ALTER INDEX IF EXISTS idx_game_name RENAME TO idx_soundtrack_name;
-ALTER INDEX IF EXISTS idx_song_game_id RENAME TO idx_song_soundtrack_id;
-ALTER INDEX IF EXISTS idx_song_game_id_song_name RENAME TO idx_song_soundtrack_id_song_name;
-ALTER INDEX IF EXISTS song_list_game_name_idx RENAME TO song_list_soundtrack_name_idx;

internal/db/migrations/000006_add_id_to_song.down.sql

@@ -1,24 +0,0 @@
--- Rollback: Remove id column and restore composite PK
-
--- Step 1: Drop indexes created in up migration
-DROP INDEX IF EXISTS idx_song_soundtrack_id;
-DROP INDEX IF EXISTS idx_song_path;
-
--- Step 2: Drop foreign key constraint
-ALTER TABLE song DROP CONSTRAINT IF EXISTS song_soundtrack_id_fkey;
-
--- Step 3: Drop new primary key
-ALTER TABLE song DROP CONSTRAINT song_pkey;
-
--- Step 4: Drop unique constraint on id
-ALTER TABLE song DROP CONSTRAINT IF EXISTS song_id_unique;
-
--- Step 5: Restore composite primary key
-ALTER TABLE song ADD CONSTRAINT song_pkey PRIMARY KEY (soundtrack_id, path);
-
--- Step 6: Drop the id column
-ALTER TABLE song DROP COLUMN id;
-
--- Step 7: Recreate original foreign key (soundtrack_id references soundtrack.id)
-ALTER TABLE song ADD CONSTRAINT song_soundtrack_id_fkey 
-    FOREIGN KEY (soundtrack_id) REFERENCES soundtrack(id);

internal/db/migrations/000006_add_id_to_song.up.sql

@@ -1,36 +0,0 @@
--- Migration: Add id column to song table and change PK from composite to single column
--- This prepares the song table for eventual UUID migration
-
--- Step 1: Add new id column (nullable initially)
-ALTER TABLE song ADD COLUMN id serial4;
-
--- Step 2: Create unique constraint on id (allows backfilling)
-ALTER TABLE song ADD CONSTRAINT song_id_unique UNIQUE (id);
-
--- Step 3: Backfill existing rows with sequential IDs
--- Use DEFAULT which pulls from the sequence
-UPDATE song SET id = DEFAULT WHERE id IS NULL;
-
--- Step 4: Verify all rows have an id
--- If this returns 0, backfill worked
--- SELECT COUNT(*) FROM song WHERE id IS NULL;
-
--- Step 5: Drop the composite primary key (soundtrack_id, path)
-ALTER TABLE song DROP CONSTRAINT song_pkey;
-
--- Step 6: Add new primary key on id column
-ALTER TABLE song ADD CONSTRAINT song_pkey PRIMARY KEY (id);
-
--- Step 7: Ensure soundtrack_id remains a foreign key to soundtrack
--- First drop existing FK if it exists (from the rename migration)
-ALTER TABLE song DROP CONSTRAINT IF EXISTS song_soundtrack_id_fkey;
-
--- Then recreate it
-ALTER TABLE song ADD CONSTRAINT song_soundtrack_id_fkey 
-    FOREIGN KEY (soundtrack_id) REFERENCES soundtrack(id);
-
--- Step 8: Create index on soundtrack_id for query performance
-CREATE INDEX IF NOT EXISTS idx_song_soundtrack_id ON song(soundtrack_id);
-
--- Step 9: Create index on path for lookups (previously part of PK)
-CREATE INDEX IF NOT EXISTS idx_song_path ON song(path);