These id fields were enriched with `@default(cuid())` information taken from the previous Prisma schema

Bug description

While in the process of upgrading from prisma 1.13, I usually run introspection after each step. so one warning kept showing even though I don’t think there’s a need for it, correct me please.

How to reproduce

I just run

npx prisma introspect

*** WARNING ***
These id fields were enriched with `@default(cuid())` information taken from the previous Prisma schema.
- Model "A", field: "id"
- Model "B", field: "id"
.
.
.etc

Expected behavior

I think it should not be shown given the schema has actually been enriched

Prisma information

model Item1 {
  id                  String                 @id @default(cuid()) @db.Char(30)
}

model Item2 {
  id                  String                 @id @default(cuid()) @db.Char(30)
}

Environment & setup

OS: Ubuntu 18 Database: MySQL 5.7 Node.js version: 14.15.1

Prisma version:
prisma               : 2.17.0
@prisma/client       : 2.17.0
Current platform     : debian-openssl-1.1.x
Query Engine         : query-engine 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at node_modules/@prisma/engines/query-engine-debian-openssl-1.1.x)
Migration Engine     : migration-engine-cli 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at node_modules/@prisma/engines/migration-engine-debian-openssl-1.1.x)
Introspection Engine : introspection-core 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at node_modules/@prisma/engines/introspection-engine-debian-openssl-1.1.x)
Format Binary        : prisma-fmt 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at node_modules/@prisma/engines/prisma-fmt-debian-openssl-1.1.x)
Studio               : 0.353.0

[omar-dulaimi]

@Jolg42 doing that I lost the following attributes from the schema:

@default(cuid())
@updatedAt

Also relation fields names have changed to their models names, like reporter changed to AbuseReporter camelcase.

It basically messes the whole schema up and I have to go through the 700 lines schema line by line to fix the issues.

So I have no choice but to undo the --force

[carlosbensant]

They mentioned something about using the @default(cuid()) and @updatedAt attributes here: https://www.prisma.io/docs/guides/upgrade-guides/upgrade-from-prisma-1/schema-incompatibilities-postgres#manually-add-the-updatedat-attribute-to-the-prisma-model

They’re well-known problems and are seen/provided as workarounds.