Hi everyone! Is there a way to enforce prisma migrate to generate BIGINT instead of BIGSERIAL for ids?

model Denomination {

id         BigInt      @unique @default(autoincrement()) @db.BigInt

symbol     String      @unique

active     Boolean

createdAt  DateTime    @default(now()) @map("created_at") @db.Timestamp(5)

updatedAt  DateTime    @default(now()) @map("updated_at") @db.Timestamp(5)

@@map("denomination")

}

Running prisma migrate, generates the following sql scrcipt

-- CreateTable

CREATE TABLE "denomination" (

"id" BIGSERIAL NOT NULL, -- Here I want BIGINT insted of BIGSERIAL

"symbol" TEXT NOT NULL,

"active" BOOLEAN NOT NULL,

"created_at" TIMESTAMP(5) NOT NULL DEFAULT CURRENT_TIMESTAMP,

"updated_at" TIMESTAMP(5) NOT NULL DEFAULT CURRENT_TIMESTAMP

);

Thanks in advance!

Unfortunately not right now. That we use

SERIAL

or its equivalents is baked in right now.

Hey @janpio, thanks for responding. Firstly, it is a best practice that Postgres suggest that serial type shouldn't be used. In my case I need to use that

BIGINT

for security reasons. Also found this issue on GitHub, I will change it by hand for now, but it would be great to have a customizable feature for this type of issue.

Yes, we know - but as we support older Postgres versions as well, we do not really have a choice until we start to generate different migrations for different versions - which comes with its own set of problems.