Prisma migrate incorrectly infers new migration needed when dbgenerated contains a string. #14917
Description
Bug description
Giving a default db generated value with a string in it leads Prisma Migrate to think a new migration is always needed:
datasource db {
provider = "cockroachdb"
// ...
}
model Test {
id BigInt @id @default(autoincrement())
foo Int
bar String @default(dbgenerated("'hello world'"))
}
How to reproduce
- Use the schema above
- Create new migration
- Run
prisma migrate devagain - See Prisma prompt for a new migration 🐞
Expected behavior
Prisma doesn't prompt to create a new migration after the first one is created.
Prisma information
See above
Environment & setup
- OS: macOS 12.4
- Database: Cockroach v22.1.5
- Node.js version: 14.17.6
Prisma Version
prisma : 4.2.1
@prisma/client : 4.2.1
Current platform : darwin
Query Engine (Node-API) : libquery-engine 2920a97877e12e055c1333079b8d19cee7f33826 (at node_modules/@prisma/engines/libquery_engine-darwin.dylib.node)
Migration Engine : migration-engine-cli 2920a97877e12e055c1333079b8d19cee7f33826 (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine : introspection-core 2920a97877e12e055c1333079b8d19cee7f33826 (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary : prisma-fmt 2920a97877e12e055c1333079b8d19cee7f33826 (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash : 2920a97877e12e055c1333079b8d19cee7f33826
Studio : 0.469.0