How to prevent Prisma from touching my existing database


#1

I have an existing database table called Operator with two fields “id” and “operator_uic_code”

I would like the corresponding GraphQL fields to be called “id” and “code”

I’ve tried the following, but it tries add a column “operator_uic_code” (and fails because it already exists)

type Operator @db(name:“operator”) {
id: Int! @id
code: Int! @db(“operator_uic_code”)
}

How to prevent Prisma from trying to create the database column “operator_uic_code” and instead use the existing column? I’ve tried “migrations:false”