Error in migration when updating enum

[PauloPraf]

Hi Prisma Team! Prisma Migrate just crashed.

Command

migrate dev

Versions

Name	Version
Platform	windows
Node	v16.15.0
Prisma CLI	4.2.1
Engine	2920a97877e12e055c1333079b8d19cee7f33826

Error

Error: Error in migration engine.
Reason: [migration-engine\connectors\sql-migration-connector\src\sql_renderer\postgres_renderer.rs:908:22] We should only be setting a changed default if there was one on the previous schema and in the next with the same enum.

Please create an issue with your `schema.prisma` at
https://github.com/prisma/prisma/issues/new

[danstarns]

Hey @PauloPraf,

Please could you share with us your Prisma schema?

[OscarMulder]

I had this exact same error with the following schema change.

Before:

model User {
  id            String    @id @default(cuid())
  name          String?
  email         String?   @unique
  emailVerified DateTime?
  image         String?
  accounts      Account[]
  sessions      Session[]
  roles         Role[]    @default([STUDENT])
}

enum Role {
  STUDENT
  STAFF
  MONITORINGMANAGER
  ADMIN
}

Changed only the enum:

enum Role {
  STUDENT
  STAFF
  STUDENTAFFAIRS
  ADMIN
}

I got the following warning beforehand:

⚠️  Warnings for the current datasource:

  • The values [MONITORINGMANAGER] on the enum `Role` will be removed. If these variants are still used in the database, this will fail.

✔ Are you sure you want create and apply this migration? … yes

However there are no records in my database with the value MONITORINGMANAGER.

[OscarMulder]

After removing the @default([STUDENT]) the migration was successfully applied.

[janpio]

Was this also about changing an enum for you @PauloPraf?

[PauloPraf]

Was this also about changing an enum for you @PauloPraf?

Yes, it was the same situation as described above.

[jkomyno]

Another report: https://prisma-errors.netlify.app/report/14266

[Jolg42]

Hi @PauloPraf 👋🏼
It looks like this was fixed in 4.7.0, could you try upgrading to that version or a more recent one?

PR: prisma/prisma-engines#3379

[Jolg42]

@PauloPraf I'll close this as it should be fixed already, let us know if it's indeed the case or if we should reopen this.