Prisma drops and recreates enum array field when running migrate even if the field has not changed

[devunt]

Bug description

Running prisma migrate dev always results in re-creating enum array field, even after applying suggested changes (which was re-creating the field)

$ prisma migrate diff --from-schema-datamodel ./prisma/schema.prisma --to-schema-datasource ./prisma/schema.prisma

[*] Changed the `posts` table
  [*] Column `content_filters` would be dropped and recreated (type changed)

How to reproduce

1. Run prisma migrate dev

Expected behavior

No difference is reported.

Prisma information

model Post {
  id                  String        @id
  ...
  contentFilters         ContentFilterCategory[] @map("content_filters")
  ...

  @@map("posts")
}

enum ContentFilterCategory {
  ADULT
  ...
  OTHER

  @@map("_content_filter_category")
}

Environment & setup

• OS: macOS 14.2
• Database: PostgreSQL 15.4
• Node.js version: v20.10.0

Prisma Version

prisma                  : 5.7.0
@prisma/client          : 5.7.0
Computed binaryTarget   : darwin-arm64
Operating System        : darwin
Architecture            : arm64
Node.js                 : v20.10.0
Query Engine (Node-API) : libquery-engine 79fb5193cf0a8fdbef536e4b4a159cad677ab1b9 (at ../../node_modules/.pnpm/@prisma+engines@5.7.0/node_modules/@prisma/engines/libquery_engine-darwin-arm64.dylib.node)
Schema Engine           : schema-engine-cli 79fb5193cf0a8fdbef536e4b4a159cad677ab1b9 (at ../../node_modules/.pnpm/@prisma+engines@5.7.0/node_modules/@prisma/engines/schema-engine-darwin-arm64)
Schema Wasm             : @prisma/prisma-schema-wasm 5.7.0-41.79fb5193cf0a8fdbef536e4b4a159cad677ab1b9
Default Engines Hash    : 79fb5193cf0a8fdbef536e4b4a159cad677ab1b9
Studio                  : 0.495.0
Preview Features        : metrics, tracing

[devunt]

After further investigation, it appears that if I change @@map("_content_filter_action") on enum to @@map("content_filter_action"), the issue is gone. Which seems the starting underscore of the mapped name is causing the issue.

[miguelff]

Hey @devunt _content_filter_action seems to be a different string than that initially reported. Mind sending us a failing and a non-failing schema, So we don't introduce noise in the reproduction? Thank you.

[SevInf]

Reproduced on latest main (5.11.0-dev), internal link.

To reproduce, run prisma migrate dev multiple times. Each migration after the first one will re-create the column and DB would never be reproved as "already in sync". For it to work, you need both @@map("_something") for and the field on the model to be a list.