Error: Schema engine error:

I'm trying to integrate supabase with prisma but getting the following error:

Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma
Datasource "db": PostgreSQL database "postgres", schema "public" at "aws-1-us-east-1.pooler.supabase.com:5432"

Error: Schema engine error:

Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma
Datasource "db": PostgreSQL database "postgres", schema "public" at "aws-1-us-east-1.pooler.supabase.com:5432"

Error: Schema engine error:

33 Replies

gabrielOP•7d ago

Please help me to fix this error. I'm not sure what the error is... Here's my schema.prisma:

generator client {
  provider = "prisma-client-js"
  output   = "../generated/prisma"
}

datasource db {
  provider = "postgresql"
  url       = env("DATABASE_URL")
  directUrl = env("DIRECT_URL")
}

model Post {
  id        Int     @id @default(autoincrement())
  title     String
  content   String?
  published Boolean @default(false)
  author    User?   @relation(fields: [authorId], references: [id])
  authorId  Int?
}

model User {
  id    Int     @id @default(autoincrement())
  email String  @unique
  name  String?
  posts Post[]
}

generator client {
  provider = "prisma-client-js"
  output   = "../generated/prisma"
}

datasource db {
  provider = "postgresql"
  url       = env("DATABASE_URL")
  directUrl = env("DIRECT_URL")
}

model Post {
  id        Int     @id @default(autoincrement())
  title     String
  content   String?
  published Boolean @default(false)
  author    User?   @relation(fields: [authorId], references: [id])
  authorId  Int?
}

model User {
  id    Int     @id @default(autoincrement())
  email String  @unique
  name  String?
  posts Post[]
}

garyaustin•7d ago

Is there more errror info. That error is only seen once here with Prisma and was relayed with a more detailed connection error. Guides: https://supabase.com/docs/guides/database/prisma https://supabase.com/docs/guides/database/prisma/prisma-troubleshooting Make sure you connection URL is correct including using postgres.instanceid for the username and no special characters in the password.

gabrielOP•7d ago

Here's my env file

DATABASE_URL=postgresql://postgres.project_id:[email protected]:6543/postgres?pgbouncer=true

# Direct connection to the database. Used for migrations
DIRECT_URL=postgresql://postgres.project_id:[email protected]:5432/postgres

DATABASE_URL=postgresql://postgres.project_id:[email protected]:6543/postgres?pgbouncer=true

# Direct connection to the database. Used for migrations
DIRECT_URL=postgresql://postgres.project_id:[email protected]:5432/postgres

And there isn't any more error I followed the docs and everything is from docs

garyaustin•7d ago

If you password does not contain special characters and your instance is in US east those look correct.

gabrielOP•7d ago

I've just created the project on supabase I don't have any special characters or number on my password Is there any other configuration on supabase?

garyaustin•7d ago

Wait. Are your URL's backwards?

gabrielOP•7d ago

the env variables are also from supabase

garyaustin•7d ago

Yeah, the connect tab shows like you have.

gabrielOP•7d ago

Is that something wrong?

garyaustin•7d ago

For serverless prisma clients

gabrielOP•7d ago

It looks same as mine

garyaustin•7d ago

I don't know of any other settings and most Prisma users here get a connection error and not this "schema engine error". I've never seen that but there is one hit in the search here from awhile back. You'll have to see if a Prisma user comes along. Your settings seem correct for serverless.

gabrielOP•7d ago

I created a "prisma" user as well by following this:

gabrielOP•7d ago

Same error with "prisma"

garyaustin•7d ago

You used postgres user in your code you showed. So would need the DB password.

gabrielOP•7d ago

I have db password too

garyaustin•7d ago

So you tried both users?

gabrielOP•7d ago

Yes tried both and same error

garyaustin•7d ago

The Postgres one with the DB password should work.

gabrielOP•7d ago

I think it looks like connection error. Is there any way to check that url manually?

garyaustin•7d ago

PSQL is a db tool you can install with locally with a local Postgres and can test it. Do you see something that says connection error?

gabrielOP•7d ago

Can I test DATABASE_URL (port 6543) on pgAdmin?

garyaustin•7d ago

Not sure. I know you can test the 5432 port. If that works the other would too. I've never used the pooler transaction port with a DB tool. There are no known issues with Prisma and Supabase.

gabrielOP•7d ago