From afe8a585357f26795ca0128ef437a3c3c7c85db2 Mon Sep 17 00:00:00 2001 From: Matt Date: Mon, 2 Feb 2026 17:17:55 +0100 Subject: [PATCH] Fix migration: skip inviteToken columns and index that already exist in production Co-Authored-By: Claude Opus 4.5 --- .../20260202000000_prototype1_improvements/migration.sql | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/prisma/migrations/20260202000000_prototype1_improvements/migration.sql b/prisma/migrations/20260202000000_prototype1_improvements/migration.sql index 388ed86..fe986db 100644 --- a/prisma/migrations/20260202000000_prototype1_improvements/migration.sql +++ b/prisma/migrations/20260202000000_prototype1_improvements/migration.sql @@ -16,9 +16,7 @@ CREATE TYPE "EligibilityMethod" AS ENUM ('AUTO', 'MANUAL'); -- AlterTable ALTER TABLE "Project" ADD COLUMN "foundedAt" TIMESTAMP(3); --- AlterTable -ALTER TABLE "User" ADD COLUMN "inviteToken" TEXT, -ADD COLUMN "inviteTokenExpiresAt" TIMESTAMP(3); +-- AlterTable (inviteToken and inviteTokenExpiresAt already exist from previous migration) -- CreateTable CREATE TABLE "FilteringRule" ( @@ -175,8 +173,7 @@ CREATE INDEX "AwardVote_projectId_idx" ON "AwardVote"("projectId"); -- CreateIndex CREATE UNIQUE INDEX "AwardVote_awardId_userId_projectId_key" ON "AwardVote"("awardId", "userId", "projectId"); --- CreateIndex -CREATE UNIQUE INDEX "User_inviteToken_key" ON "User"("inviteToken"); +-- CreateIndex (User_inviteToken_key already exists from previous migration) -- AddForeignKey ALTER TABLE "FilteringRule" ADD CONSTRAINT "FilteringRule_roundId_fkey" FOREIGN KEY ("roundId") REFERENCES "Round"("id") ON DELETE CASCADE ON UPDATE CASCADE;