@map not carried over to `makeEnum`

Given the following enum in schema.prisma

enum Role {
  ADMIN     @map("admin")

  @@map("role")
}

The generated JavaScript contains

exports.Role = makeEnum({
  ADMIN: 'ADMIN',
});

The value should be the same as inside the map

[Weakky]

Hey folks,

I think this issue stems from a misunderstanding of how @map works.

@map gives metadata to the Query Engine so that it knows the name of the model/enum field name stored in the database. @map never leaks into the client, it’s the field name that’s used in the client. eg:

Given this datamodel 👇,

model User {
  id Int @id @map("user_id")
  role Role  @map("user_role")
}

enum Role {
  ADMIN @map("admin")
}

The client should expose:

type User = {
  id: number
  role: Role
}

type Role = {
  ADMIN: 'ADMIN'
}

It’s only internally that the Query Engine will use these @map annotations to do the mappings. These @map values aren’t expected to be sent over the wire. They’re roughly used, for instance, to:

• Select the proper columns. eg: SELECT user_id AS id, user_role AS role FROM ...
• Compare against the actual enum values stored in the DB. eg: SELECT ... FROM ... WHERE user_role = "admin" 👈 "admin", not "ADMIN" here.

Hope that makes sense, I’m closing now. Feel free to ask further questions/re-open if you still think that’s wrong.

[pantharshit00]

I can reproduce this with 2.16.0-dev.67. We should definitely export the correct value.

It works when you insert data as we use postgres/mysql enums under the hood.