Fix migration transaction poisoning: ADD COLUMN IF NOT EXISTS
Migrations used try/except around ADD COLUMN inside a single engine.begin() block. When a 'column already exists' error was caught, asyncpg left the transaction in aborted state, causing all subsequent DDL in the block to fail with InFailedSQLTransactionError. Replace with IF NOT EXISTS to prevent the error entirely. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
e7e1fda9f6
commit
bc874ac9ff
25 changed files with 302 additions and 302 deletions
|
|
@ -26,9 +26,9 @@ async def run_migration():
|
|||
|
||||
# Add arrival tracking columns to newbook_daily_occupancy table
|
||||
arrival_columns = [
|
||||
"ALTER TABLE newbook_daily_occupancy ADD COLUMN arrival_count INTEGER",
|
||||
"ALTER TABLE newbook_daily_occupancy ADD COLUMN arrival_booking_ids JSONB",
|
||||
"ALTER TABLE newbook_daily_occupancy ADD COLUMN arrival_booking_details JSONB",
|
||||
"ALTER TABLE newbook_daily_occupancy ADD COLUMN IF NOT EXISTS arrival_count INTEGER",
|
||||
"ALTER TABLE newbook_daily_occupancy ADD COLUMN IF NOT EXISTS arrival_booking_ids JSONB",
|
||||
"ALTER TABLE newbook_daily_occupancy ADD COLUMN IF NOT EXISTS arrival_booking_details JSONB",
|
||||
]
|
||||
|
||||
for sql in arrival_columns:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue