Prisma Studio: Unsupported "@default()" declaration

[BluSimmon]

Background

@default() values are placing as default values when inserting rows in old version of studio.
However, @default() values are no longer being managed by Prisma Schema API on Prisma Studio when inserting rows.

Reproduction

Simply clicking on Add Record / Insert Row within selected table viewer on Prisma Studio.

Actual Behaviour

Default values are no longer exist.
It is now showing (empty string) instead of (default value).
Example image below, captured from the latest version of Prisma Studio.

Expected Behaviour

The specified cell with @default() declaration should be managed by Prisma Schema API when no manual inputs.
Example Image below is captured from the older version of Prisma Studio.

Environment

Browser: Microsoft Edge 134.0.3124.66 (Official) (64-bit)
Database: MySQL 8

Schema (same for both version)

model UserRole {
  id             String                 @id @default(ulid())
  weight         Int                    @default(0)
  name           User_Role              @unique
  displayName    String
  ...
}

enum User_Role {
  User
  Admin
}

Older version:

"@prisma/client": "^6.16.2",
"prisma": "^6.16.2",

Newer version:

"@prisma/adapter-mariadb": "^7.7.0",
"@prisma/client": "^7.7.0",
"prisma": "^7.7.0",

[sorenbs]

Hi @BluSimmon — thanks for the careful before/after comparison, this is a real gap in the new Studio. Some context: Studio v7 introspects your database directly rather than reading the Prisma schema, which is why schema-level defaults like ulid() (which only exist in Prisma Client, not in the database) no longer show up. What we plan to do: surface database-level defaults (your MySQL columns' actual DEFAULT expressions) in the insert flow, and omit untouched columns from the INSERT so the database applies its defaults — that restores the behavior for everything the database knows about. Prisma-Client-level defaults (ulid(), cuid(), nanoid()) are unfortunately invisible to a database-connected tool; documenting that limitation clearly will be part of the work. Keeping this open to track it.