From c60a7ba1ab14dde168734ab59895e79a91a7b8f7 Mon Sep 17 00:00:00 2001
From: Mondo Diaz <armando.m.diaz@boeing.com>
Date: Wed, 28 Jan 2026 20:27:46 +0000
Subject: [PATCH] Add rollback after failed migration to allow subsequent
 migrations to run

When a migration fails, the transaction is left in a failed state. Without
rollback, all subsequent migrations fail with "current transaction is aborted".
This was preventing the team_id column from being added to projects.
---
 backend/app/database.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/backend/app/database.py b/backend/app/database.py
index d6f6673..1e6a3c7 100644
--- a/backend/app/database.py
+++ b/backend/app/database.py
@@ -347,6 +347,7 @@ def _run_migrations():
                 conn.execute(text(migration))
                 conn.commit()
             except Exception as e:
+                conn.rollback()
                 logger.warning(f"Migration failed (may already be applied): {e}")