console-and-connections

Use Prisma Console workflows for project visibility, data inspection, and connection setup.

Priority

HIGH

Why It Matters

Many Prisma Postgres tasks are quickest in the Console: viewing Studio data, checking metrics, and retrieving connection details. This avoids unnecessary API or CLI work for simple operational tasks.

Console workflow

Open https://console.prisma.io.
Select workspace and project.
Use dashboard metrics for usage and billing visibility.
Open the Studio tab in the sidebar to inspect and edit data.

Local Studio

You can also inspect data locally:

npx prisma studio

Linking an existing project

If the Prisma Postgres database already exists, link the local project instead of provisioning a new one:

prisma postgres link

For CI or non-interactive usage:

prisma postgres link --api-key "<your-api-key>" --database "db_..."

This command updates or creates .env with DATABASE_URL. If the project is already linked, use --force to re-link. After linking, run prisma generate, then prisma migrate dev if you need to apply the schema.

Connection setup

For direct PostgreSQL tools and drivers:

Generate/copy direct connection credentials from the project connection UI.
Use the resulting PostgreSQL URL as DATABASE_URL for pg and @prisma/adapter-pg.
For Prisma Postgres direct TCP, include sslmode=require.

Typical direct TCP format:

DATABASE_URL="postgres://identifier:key@db.prisma.io:5432/postgres?sslmode=require"

Management API connection responses expose both endpoints.direct (db.prisma.io:5432) and endpoints.pooled (pooled.db.prisma.io:5432); prefer those fields over the deprecated flat connectionString. Connection secrets are shown once at creation (one-time view); store them immediately.

Adapter choices

Standard Node.js apps: prefer @prisma/adapter-pg with the direct TCP URL above.
Edge/serverless runtimes: use @prisma/adapter-ppg with @prisma/ppg only when you specifically need the Prisma Postgres serverless driver.

2.3 KiB Raw Blame History