Prisma connection guide
Prisma PostgreSQL Connection String
Set DATABASE_URL for Prisma, keep pooled application traffic separate from direct migration traffic, and encode special characters correctly.
Use the connection value generated by Prisma, keep it in an environment variable, and test it before changing application code. The URI shape below is a template, not a credential to paste unchanged.
- URI scheme
- postgresql://
- Default PostgreSQL port
- 5432
- Credential handling
- Environment variable or secret manager
- First test
- npx prisma db pull
Connection string template
postgresql://USER:PASSWORD@HOST:5432/DB_NAME?schema=public&sslmode=requireReplace every uppercase placeholder. Percent-encode reserved characters in URI usernames and passwords.
Environment variable
DATABASE_URL="postgresql://USER:PASSWORD@HOST:5432/DB_NAME?schema=public"Where to get the Prisma values
Put the URI in your environment and reference env("DATABASE_URL") from the PostgreSQL datasource in schema.prisma. Current Prisma configuration can also place datasource URLs in prisma.config.ts.
The failure mode worth checking first
Percent-encode reserved characters in the username and password. With a transaction pooler, migrations and introspection may need a separate direct URL because those commands expect a stable database session.
Test the connection
Run a cheap read-only command before migrations or application startup. That separates network, TLS, and authentication errors from framework configuration problems.
Connection check
npx prisma db pullOpen it in PostgresGUI
Paste the PostgreSQL URI into PostgresGUI or enter the same host, port, database, user, password, and SSL mode as separate fields. A desktop connection is useful for checking the visible schemas and role permissions before debugging the application layer.
Questions that come up
Should the connection string be committed to Git?
No. Commit an example with placeholders and load the real value from an environment variable or secret manager.
Why does a password with @ or # break the URI?
Those characters have meaning inside a URL. Percent-encode the username and password, or use a structured connection API instead of assembling a URL by hand.
Do I need sslmode=require?
Most hosted PostgreSQL services require TLS. For strict certificate and hostname verification, use sslmode=verify-full with the provider's trusted root certificate when the client supports it.