bug - changing primary key names

[brecht-derooms]

Coming from a db that is not managed by prisma but by another ORM I noticed that it generates a.

• drop constraint
• rename constraint
• new constraint.

I assume this is a minor bug and that the rename constraint shouldn't have been generated in this case or that the add constraint should have not bene generated but in that case the SQL syntax is not entirely correct either (it might require to "alter table" statements iirc).

-- AlterTable
ALTER TABLE "product_reservations" DROP CONSTRAINT "pk-product_reservations",
RENAME CONSTRAINT "pk-product_reservations" TO "product_reservations_pkey",
... column changes
ADD CONSTRAINT "product_reservations_pkey" PRIMARY KEY ("id");

Easy to fix manually though.

[Brendonovich]

PCR doesn't manage migration SQL, you'll want to report this over in the Prisma repo.