Bug: Constraints not well-handled by Studio

I am not sure if this is an issue with Prisma or Blitz or Supabase.

When I run blitz prisma migrate dev, the default value for id is set in Supabase to extval('"User_id_seq" (truncated—exactly like that).

This is the corresponding schema in Prisma: id Int @id @default(autoincrement()).

Is this a bug? Or am I doing something wrong?

[kiwicopple]

CREATE TABLE "Test" (
    "id" BIGSERIAL NOT NULL,

    CONSTRAINT "Test_pkey" PRIMARY KEY ("id")
);

I see - they are adding it as constraint, and it seems that Studio isn’t great at handling constraints. This is a bug for us to fix! I’ll edit the title and let the Frontend team know

See also: https://github.com/supabase/supabase/issues/7653

We don’t handle multiple constraints very well

[joshenlim]

just fyi, this is happening as the dashboard is attempting to do some formatting against the default value of the column to remove the type cast incorrectly - i’ll look into a temp fix for this, but the longer term fix that I’ll look into as well is just have the Column side panel editor not do formatting from PG’s side (e.g not formatting 'some text'::text to 'some text', just leave it as it is)

ref ColumnEditor.utils.ts -> unescapeLiteral at line 199