Question

Hi,
I'm not sure if this is a bug or if prisma can work around this.
When I have an optional relation defined (using an D1 DB) with the default onDelete: SetNull and generate a migration to update a table, the relation is lost due to the migration deleting the data.

How to reproduce (optional)

Take the following migration for example:

CREATE TABLE "new_Product" (
    "id" TEXT NOT NULL PRIMARY KEY,
    "createdAt" DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
    "updatedAt" DATETIME NOT NULL,
    "name" TEXT NOT NULL,
    "description" TEXT,
    ...some more rows
);
INSERT INTO "new_Product" ("createdAt", "description", "id", "name", "updatedAt", ...) SELECT "createdAt", "description", "id", "name", "updatedAt", ... FROM "Product";
DROP TABLE "Product";
ALTER TABLE "new_Product" RENAME TO "Product";

In another table with an optional relation to Product, the productId column now is NULL for every row...
The same problem exists with ManyToMany relations...

Questions:

• Is that known and expected?
• Are there workarounds for the Migration? I'd rather avoid updating my schema to use onDelete: Restrict everywhere because then I deleting those entries (explicitely in my code) becomes more complex

Thanks in advance!

Expected behavior (optional)

No response

Information about Prisma Schema, Client Queries and Environment (optional)

// Add your schema.prisma

// Add any relevant Prisma Client queries here

• OS:

• Database:

• Node.js version:

• Run prisma -v to see your Prisma version and paste it