Prisma schema: Remove empty dbgenerated() attribute

[Jolg42]

Example

 createdAt DateTime @default(dbgenerated())

In the times of old, an empty dbgenerated() in a @default field attribute was used by the introspection in fields, where we could not parse the default value correctly. Later on in the migration engine, we started to use it to pass custom SQL, and an empty value is in general just skipped.

In the real world, an empty dbgenerated() can cause drift and weird panics. We allow it in the PSL for backwards-compatibility. We should make it a validation error. The user can just db pull the database and get a non-empty value to the field’s default attribute.

• First: investigate why we still create it during introspection for some schemas
  • https://github.com/prisma/team-orm/issues/162
• Make it a validation error
• Close? https://github.com/prisma/schema-team/issues/215
• Investigate Empty dbgenerated() still breaking for Unsupported() types #15654
• Remove from https://github.com/prisma/prisma/blob/main/packages/client/src/__tests__/integration/happy/enums/schema.prisma
• Check occurrences from https://github.com/search?q=org%3Aprisma+%22dbgenerated%28%29%22&type=code&p=1
• Release notes draft
• Test how it looks with the VS Code extension

[janpio]

https://github.com/search?q=repo%3Aprisma%2Fintrospection-ci%20dbgenerated()&type=code

[Jolg42]

Note:
Just found these 2 small private issues:
https://github.com/prisma/schema-team/issues/215
https://github.com/prisma/team-orm/issues/162

[janpio]

Docs PR prepared for when this got implemented: prisma/docs#5007

[janpio]

Survey to collect feedback on why users might still be using it: #20077