Introspection bug for @@unique name on MySQL

[Jolg42]

In MySQL (8.0.19) the @@unique key is named email after introspection

create table users (
  id serial primary key not null,
  email varchar(50) not null,
  name varchar(50) not null,
  unique(email, name)
);
insert into users (email, name) values ('ada@prisma.io', 'Ada');

Introspection output

generator client {
  provider = "prisma-client-js"
  output   = "***"
}

datasource mysql {
  provider = "mysql"
  url      = "***"
}

model users {
  email String
  id    Int    @default(autoincrement()) @id
  name  String

  @@unique([email, name], name: "email")
}

This works in PostgreSQL, the @@unique key is named users_email_name_key after introspection

create table users (
  id serial primary key not null,
  email text not null,
  name text not null,
  unique(email, name)
);
insert into users ("email", "name") values ('ada@prisma.io', 'Ada');

Introspection output

generator client {
  provider = "prisma-client-js"
  output = "***"
}

datasource pg {
  provider = "postgresql"
  url = "***"
}

model users {
  email String
  id    Int    @default(autoincrement()) @id
  name  String

  @@unique([email, name], name: "users_email_name_key")
}

[Jolg42]

Looks like the default naming is different in MySQL and can be set like this

unique key users_email_name_key(email, name)