Introspect in 2.11.0 changes all updatedAt properties' types to timestamptz and comments them out

Bug description

Using the latest release, 2.11.0, introspect will change all updatedAt properties’ types to timestamptz and comment them out.

How to reproduce

Given a PostgreSQL table:

CREATE TABLE IF NOT EXISTS "contact" (
  "id" uuid NOT NULL DEFAULT uuid_generate_v4(),
  "updatedAt" timestamp(6) with time zone NOT NULL DEFAULT now(),
  PRIMARY KEY ("id")
);

Model prior to introspection:

model contact {
  id                 String              @id @default(dbgenerated())
  updatedAt          DateTime            @default(now()) @updatedAt

Model after introspection:

model contact {
  id                 String              @id @default(dbgenerated())
  // This type is currently not supported.
  // updatedAt       timestamptz         @default(dbgenerated())

Expected behavior

Expect introspect to not change the schema.

Environment & setup

• OS: Windows
• Database: PostgreSQL
• Node.js version: 12.16.1
• Prisma version: 2.11.0

[TLadd]

Would it be possible to suppress the warnings with a flag and restore the old behavior? It’s reasonable to warn about the use of timestamptz if they lead to unexpected behavior but for apps that were working before it would be nice to have an upgrade path without having to migrate the database. I would expect a lot of people using postgres would be using timestamptz since their docs explicitly suggest it over timestamp.

[xiaoyu-tamu]

Could we just keep the old behavior if user didn’t enable the nativeType preview feature?