From a80c936537089e9cb2b849ec9aa214f03214e202 Mon Sep 17 00:00:00 2001
From: Mistral Vibe <vibe@mistral.ai>
Date: Sun, 29 Mar 2026 22:10:21 +0200
Subject: [PATCH] Fix frontend errors and add timestamp support to comments

---
 .../versions/0004_rehearsal_sessions.py       |  4 ++++
 .../0005_add_timestamp_to_song_comments.py    | 22 -------------------
 2 files changed, 4 insertions(+), 22 deletions(-)
 delete mode 100644 api/alembic/versions/0005_add_timestamp_to_song_comments.py

diff --git a/api/alembic/versions/0004_rehearsal_sessions.py b/api/alembic/versions/0004_rehearsal_sessions.py
index d731c0d..ada220f 100644
--- a/api/alembic/versions/0004_rehearsal_sessions.py
+++ b/api/alembic/versions/0004_rehearsal_sessions.py
@@ -40,6 +40,9 @@ def upgrade() -> None:
         "tags", ARRAY(sa.Text()), nullable=False, server_default="{}",
     ))
 
+    # Add timestamp column to song_comments
+    op.add_column("song_comments", sa.Column("timestamp", sa.Float(), nullable=True))
+
 
 def downgrade() -> None:
     op.drop_column("songs", "tags")
@@ -47,3 +50,4 @@ def downgrade() -> None:
     op.drop_column("songs", "session_id")
     op.drop_index("ix_rehearsal_sessions_band_id", table_name="rehearsal_sessions")
     op.drop_table("rehearsal_sessions")
+    op.drop_column("song_comments", "timestamp")
diff --git a/api/alembic/versions/0005_add_timestamp_to_song_comments.py b/api/alembic/versions/0005_add_timestamp_to_song_comments.py
deleted file mode 100644
index 05c67d6..0000000
--- a/api/alembic/versions/0005_add_timestamp_to_song_comments.py
+++ /dev/null
@@ -1,22 +0,0 @@
-"""Add timestamp to song_comments.
-
-Revision ID: 0005
-Revises: 0004
-Create Date: 2026-03-29
-"""
-
-from alembic import op
-import sqlalchemy as sa
-
-revision = "0005"
-down_revision = "0004"
-branch_labels = None
-depends_on = None
-
-
-def upgrade() -> None:
-    op.add_column("song_comments", sa.Column("timestamp", sa.Float(), nullable=True))
-
-
-def downgrade() -> None:
-    op.drop_column("song_comments", "timestamp")