Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions content/200-orm/400-tools/06-prisma-studio.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -172,6 +172,32 @@ Support for CockroachDB and MongoDB is not currently available but may be added

## Troubleshooting

### PostgreSQL: "unrecognized configuration parameter 'schema'" error

When connecting to PostgreSQL databases, you may encounter this error if your connection string includes the `schema` query parameter:

```terminal wrap
unrecognized configuration parameter "schema"
```

This happens because the new Studio is standalone and passes your connection URL directly to the PostgreSQL driver without any processing. The URL you provide—whether via `prisma.config.ts` or the `--url` flag—must be a valid PostgreSQL connection string that only uses [standard PostgreSQL connection parameters](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-PARAMKEYWORDS).

The `schema` parameter was a custom Prisma ORM parameter that worked in v6 and earlier, but PostgreSQL itself doesn't recognize it.

To resolve this issue, use the standard `search_path` parameter instead:

```terminal
# ❌ This will cause an error
postgresql://user:password@host:port/database?schema=my_schema

# ✅ Use this instead
postgresql://user:password@host:port/database?options=-c%20search_path%3Dmy_schema
```

Alternatively, you can remove the schema parameter entirely if you're using the default `public` schema, as PostgreSQL defaults to it automatically.

For more details, see the related [GitHub issue](https://github.com/prisma/studio/issues/1363#issuecomment-3561040763).

### Terminal: Failed to run script / Error in Prisma Client request

Caching issues may cause Prisma Studio to use an older version of the query engine. You may see the following error:
Expand Down
Loading