Prisma 4.6.0 drops and recreates enum field when running db push even if the field has not changed

Bug description

I just updated from Prisma 4.5.0 to 4.6.0 and now every time I run npx prisma db push, even if I haven’t changed anything in schema.prisma, Prisma wants to drop and recreate an enum field. I get this message:

The `roles` column on the `User` table would be dropped and recreated. This will lead to data loss

If I choose to ignore the warning all my data in the roles column is reset.

After testing with multiple changes to my schema and simplifying it to the most basic form (included below) I downgraded to Prisma 4.5.0 and everything works as expected there. I’ve reconfirmed the problem exists by going back to Prisma 4.6.0.

How to reproduce

1. Use the provided basic schema.prisma. Pay attention to the roles field, which is an enum.
2. Create at least one row in the user table containing a value for the roles field.
3. Run npx prisma db push multiple times without changing anything in schema.prisma.
4. You will see The rolescolumn on theUser table would be dropped and recreated. This will lead to data loss, and if you accept the warning the data in the roles column will be reset.

Expected behavior

The roles enum column is not being changed in schema.prisma so it shouldn’t be dropped and recreated when running npx prisma db push.

Prisma information

model User {
  id                    Int               @id @default(autoincrement())
  username              String            @unique @db.VarChar(32)
  roles                 Role[]            @default([COLLECTOR])
}

enum Role {
  ADMIN
  COLLECTOR
}

// Add your code using Prisma Client

Environment & setup

• OS: Ubuntu Linux
• Database: PostgreSQL 14.2
• Node.js version: 18.0.0

Prisma Version

4.6.0

[jansedlon]

@Jolg42 4.6.1-dev.1 fixed it for me

[Jolg42]

@alexisbellido @rcbevans @bsproul @hoghweed @davidlumley Could you try to update prisma and @prisma/client to the 4.6.1-dev.1 internal patch version that includes the fixes and let us know if that solves your issue?

We will wait for some confirmations before we publish the official patch to latest.