Bug description
ReIntrospection doesn't retain @updatedAt attribute.
How to reproduce
schema.prisma
model User {
id String @id
createdAt DateTime @default(now())
updatedAt DateTime @updatedAt
}
- Either migrate or use the following SQL
CREATE TABLE `User` (
`id` varchar(191) COLLATE utf8mb4_unicode_ci NOT NULL,
`createdAt` datetime(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3),
`updatedAt` datetime(3) NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
-
Run prisma introspect --experimental-reintrospection
-
The @updatedAt attribute is lost.
Internal repo: https://github.com/prisma/re-introspection-ci/tree/master/re-introspection-analysis/output/mysql_private/migrate-default-updated-at
Expected behavior
@updatedAt should be retained.
Prisma information
Prisma CLI: 2.5.0-dev.67
Bug description
ReIntrospection doesn't retain
@updatedAtattribute.How to reproduce
schema.prismaRun
prisma introspect --experimental-reintrospectionThe
@updatedAtattribute is lost.Internal repo: https://github.com/prisma/re-introspection-ci/tree/master/re-introspection-analysis/output/mysql_private/migrate-default-updated-at
Expected behavior
@updatedAtshould be retained.Prisma information
Prisma CLI:
2.5.0-dev.67